Skip to main content
Chronosphere Observability Platform applies system limits to protect itself from failures caused by abnormal traffic patterns, such as sudden, unexpected spikes in data ingestion. For organizations that use consumption pricing, consumption system limits restrict rapid increases in metrics, logs, and traces volume. The Consumption System Limits dashboard is the source of truth for the limits enforced in your tenant. Use it to view thresholds, utilization, and data dropped by system limit enforcement. Consumption system limits apply separately from contract credit consumption and user-configured budgets. Contact Chronosphere Support to request an adjustment to these limits. Observability Platform also applies data validation, ingestion, and query protections. Learn more about the protections for the following data types:
  • Events: Ingest rate caps and field-level validation for change events.
  • Logs: Maximum individual log size and label length constraints.
  • Metrics: Label size, label count, total series byte limits, and late- or future-arriving data windows.
  • Queries: Per-query scale protections, browser truncation limits, resource balancing, and automated source rate limits.
  • Traces: Tag size, span timing validity, trace span count, and per-pod ingest caps.

​
Monitor capacity limits

For organizations that use capacity pricing, Chronosphere enforces license capacity limits for telemetry data. Exceeding these limits can put your organization at risk of dropping data. The type of data that’s dropped depends on the limit exceeded. Exceeding your organization’s license capacity limits can cause you to hit the defined system limits, which shouldn’t occur under normal operating circumstances. To prevent your system from reaching system limits, use the following tools and information to ensure that your Observability Platform tenant remains under your license capacity limit at all times: