> For the complete documentation index, see [llms.txt](https://docs.bluerock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluerock.io/bluerock-dashboard/bluerockccpd-platform-overview.md). # BluerockCCPD Platform Overview ### Introduction BlueRockCCPD is a centralized observability and operational monitoring platform designed for monitoring MCP infrastructure, telemetry activity, sessions, alerts, and operational analytics. The platform combines dashboard visualization, telemetry ingestion, GraphQL services, authentication, analytics, and graph-based investigation capabilities into a unified deployment. BlueRockCCPD provides visibility into operational activity across MCP environments and enables users to monitor infrastructure, investigate events, analyze telemetry, visualize relationships between entities, and access operational dashboards and reports through a centralized interface. Key capabilities include: * MCP infrastructure visibility * Event and telemetry monitoring * Session tracking * Topology exploration * Alert monitoring * Analytics dashboards * Operational reporting * Graph-based investigation and tracing *** ## Platform Architecture Overview BlueRockCCPD is a modular, cloud-native platform that provides centralized observability, monitoring, analytics, and policy management for BlueRock deployments. The platform collects operational data from monitored environments, processes and correlates telemetry, and presents actionable insights through a unified dashboard. The platform consists of the following functional capabilities: | Capability | Description | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | **Data Collection** | Collects telemetry, events, alerts, and operational data from BlueRock Runtime, MCP applications, AI agents, and monitored infrastructure. | | **Data Processing** | Processes, enriches, and correlates collected data to generate operational insights and policy events. | | **Monitoring and Analytics** | Provides dashboards, metrics, analytics, and health monitoring for BlueRock deployments. | | **Policy Management** | Supports centralized policy configuration and operational monitoring across monitored environments. | | **Graph-based Investigation** | Enables relationship visualization and investigation of entities, sessions, events, and telemetry. | | **Authentication and Access Control** | Secures platform access through authentication and role-based authorization. | This architecture enables organizations to monitor operational activity, investigate events, analyze telemetry, and visualize relationships across BlueRock deployments through a centralized interface. *** ## Core Data Model BlueRockCCPD organizes operational data into interconnected entities that can be explored and analyzed through dashboards, reports, and graph-based investigations. A typical operational flow consists of: ``` Host └─ MCP Server └─ MCP Agent └─ Session └─ Events └─ Tools ``` This relationship model enables users to trace activity across hosts, MCP servers, MCP agents, sessions, and operational events. *** ## Dashboard Access The platform is accessed through HTTPS endpoints. ### Dashboard URLs | Service | URL | | ------------- | --------------------------------------- | | Dashboard | [https://localhost](https://localhost/) | | OTLP Endpoint | | *** ### HTTPS Access The dashboard uses HTTPS with a self-signed certificate. During initial access, the browser may display a security warning. Accept the warning to continue accessing the dashboard. *** ## Exposed Ports | Port | Protocol | Purpose | | ---- | -------- | ---------------------------------------------- | | 443 | HTTPS | Dashboard, Grafana, Authentication, API Access | | 8080 | HTTP | OTLP event processing | *** ## Authentication and Authorization BlueRockCCPD uses WorkOS AuthKit for authentication and session management. Authentication is enforced before users can access dashboard functionality, APIs, analytics, and monitoring data. #### Authentication Flow The authentication process is performed as follows: 1. User navigates to the dashboard. 2. Frontend requests are routed through Nginx. 3. Nginx validates authentication using `auth_request`. 4. Unauthenticated users are redirected to `/login`. 5. WorkOS AuthKit performs authentication. 6. WorkOS redirects users to `/auth/callback`. 7. Authentication tokens are generated. 8. Session cookies are stored for authenticated requests. 9. Subsequent requests use the authentication cookie for validation. *** ### Role-Based Access Control (RBAC) BlueRockCCPD supports role-based access control for managing access to platform functionality. #### Supported Roles | Role | Description | | -------- | ----------------------------- | | Admin | Full platform access | | Operator | Operational monitoring access | | Viewer | Read-only access | #### Supported Capabilities Role assignments determine access to: * Dashboard views * Alerts * Telemetry data * Analytics dashboards * GFL queries * Reports * Platform operations *** ## Dashboard Capabilities The platform provides visibility into operational activity across the MCP ecosystem. ### Dashboard Features The dashboard supports: * Topology visualization * Timeline analysis * Graph exploration * Event monitoring * Session visibility * Alert visibility * Telemetry analysis * Analytics dashboards * Report generation *** ## Event Processing and Telemetry BlueRockCCPD processes telemetry and operational events using OTLP over HTTP. Events are collected, processed, enriched, and stored for operational monitoring and analytics. ### Telemetry Configuration BlueRockCCPD supports multiple methods for sending telemetry and operational events to the platform using OpenTelemetry Protocol (OTLP) over HTTP. Events can be sent using either of the following methods: * Configure an OpenTelemetry Collector using the `otel-config.yaml` configuration file. * Configure the BlueRock client using the `bluerock.toml` configuration file and specify the OTLP HTTP endpoint. **Example:** ``` [otlp.http]url = "http://:8080/" ``` Regardless of the configuration method used, events are ingested by the BlueRock platform and become available for dashboards, reports, alerts, analytics, and graph-based investigations. ### Event Visibility The dashboard provides visibility into: * Alert timelines * Event metadata * Event relationships * Host activity * Session activity * Real-time telemetry ### Telemetry Pipeline The telemetry pipeline includes: * OTLP event processing * Session telemetry * MCP activity monitoring * Event aggregation * Operational analytics Telemetry information is used throughout the platform for dashboards, analytics, reporting, alerts, and investigations. *** ## Graph Filter Language (GFL) BlueRockCCPD supports Graph Filter Language (GFL) for querying, filtering, aggregating, and analyzing entities within the platform. GFL enables users to investigate relationships, filter entities, generate aggregations, and visualize operational activity. ### GFL Features GFL supports: * Entity filtering * Query pipelines * Aggregation * Timeline analysis * Visualization transforms * Graph filtering #### Example Queries ``` gfl "mc.state == 'active'" ``` ``` gfl "mc | count by mc.state" ``` ``` gfl "mc | count by mc.state | bar" ``` #### GFL CLI Location ``` /usr/local/bin/gfl ``` *** ## Operational Monitoring BlueRockCCPD supports operational monitoring workflows across MCP infrastructure, telemetry, sessions, alerts, and analytics. Users can: * Monitor MCP agents * Monitor MCP servers * Analyze sessions * Review telemetry activity * Investigate alerts * Analyze event timelines * Explore entity relationships * Monitor analytics dashboards Operational data is available through dashboards, reports, alerts, graph exploration views, and analytics interfaces. *** ## Troubleshooting ### Common Checks Perform the following checks during troubleshooting: * Dashboard accessibility * Telemetry visibility * Event availability * Graph loading * Dashboard refresh behavior *** ## Health Endpoints ``` curl -sk https://localhost/health ``` ``` curl -s http://localhost:8080/health ``` ``` curl -s http://localhost:8123/ping ``` ### Useful Commands ``` docker logs -f bluerockccpd ``` ``` docker exec bluerockccpd s6-svstat /run/service/hramp ``` *** ## FAQ ### Why does the browser show "Not Secure"? The dashboard uses a self-signed certificate. Accept the browser warning during initial access. ### Why are some dashboard panels empty? Some dashboard panels require incoming event traffic before metrics and visualizations are displayed. ### Why are graphs not loading? Verify telemetry visibility, active event traffic, selected filters, and selected time ranges. ### When should GFL be used? GFL should be used when filtering entities, investigating operational activity, tracing relationships, analyzing sessions, or generating custom operational insights. ### What is the difference between dashboards and graph exploration? Dashboards provide summarized operational visibility, while graph exploration enables users to investigate relationships, dependencies, sessions, and activity across entities in greater detail. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bluerock.io/bluerock-dashboard/bluerockccpd-platform-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.