| CCC.Monitor.CP01 | Custom Metric Ingestion | The service can receive user-defined, numeric time-series data points pushed by applications or external systems through its API, in addition to the metrics it collects automatically from provider resources. | 4 |
| CCC.Monitor.CP02 | Distributed Tracing | The service may be configured to collect traces that link a single request to the resulting operations in downstream components and external systems, providing an end-to-end view of a transaction. | 2 |
| CCC.Monitor.CP05 | Service Level Objective Monitoring | The service may be configured to evaluate user-defined service level objectives against service level indicators derived from collected metrics, and to report the remaining error budget. | 1 |
| CCC.Monitor.CP06 | Synthetic Monitoring | The service may be configured to run scripted sample user interactions against an application on a schedule from provider-operated locations, in order to identify issues before real users are impacted. | 2 |
| CCC.Monitor.CP07 | Uptime Monitoring | The service may be configured to probe an endpoint from external provider-operated locations on a schedule and record whether it is reachable and responding. | 3 |
| CCC.Monitor.CP08 | Application Performance Monitoring | The service may be configured to collect application-level telemetry such as request latency, error rates, and dependency calls through instrumentation, in order to monitor performance and user experience. | 1 |
| CCC.Monitor.CP09 | Dashboards | The service can present metrics, alerts, service level objectives, and uptime results in user-defined visual dashboards that may be shared with other users. | 2 |
| CCC.Monitor.CP10 | Alert-Triggered Actions | The service may be configured to invoke an automated action, such as a workflow, a function, or a scaling operation, when an alert condition is met, in addition to emitting a notification. | 2 |
| CCC.Monitor.CP11 | Integration with External Tools | The service may be configured to forward alerts, notifications, and metric data to external systems such as incident management, ticketing, or third-party observability platforms. | 4 |
| CCC.Monitor.CP12 | Agent-Based Telemetry Collection | The service can collect metrics and traces from compute instances through a provider-supplied agent that runs on the instance and authenticates to the service using the instance identity or a configured credential. | 4 |
| CCC.Monitor.CP13 | Alert Suppression | The service may be configured to suppress or snooze alert notifications for a period of time or for matching conditions, so that alerts are not delivered during maintenance or known incidents. | 1 |
| CCC.Monitor.CP14 | Cross-Account Monitoring Scope | The service may be configured to aggregate metrics from multiple accounts, subscriptions, or projects into a single monitoring scope, so that users of the scope can view telemetry across tenancy boundaries. | 1 |