Skip to main content

Alert on Telemetry Ingestion Volume

CCC.Monitor.CN10 · Observability

Ensure that a flood of metric series or data points is detected before the resulting charges accrue.

Related Capabilities

IDTitleDescription
CCC.Monitor.CP01Custom Metric IngestionThe 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.
CCC.Monitor.CP10Alert-Triggered ActionsThe 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.
CCC.Monitor.CP11Integration with External ToolsThe service may be configured to forward alerts, notifications, and metric data to external systems such as incident management, ticketing, or third-party observability platforms.
CCC.Monitor.CP12Agent-Based Telemetry CollectionThe 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.

Related Threats

IDTitleDescription
CCC.Monitor.TH06Telemetry Volume Inflates Monitoring CostsCustom metrics and agent-collected telemetry are billed per metric series and per data point, and alert-triggered actions may invoke external systems that charge per request. A misconfigured or compromised workload can publish high-cardinality metrics or fire alerts at high frequency, and the resulting charges accrue before the pattern is detected. This impacts the availability of the monitoring budget and of systems whose scaling depends on it.

Assessment Requirements

IDTextApplicability
CCC.Monitor.CN10.AR01When telemetry ingestion for the service exceeds a user-defined volume or series-count threshold, the service MUST generate an alert.tlp-clear, tlp-green, tlp-amber, tlp-red