Skip to main content
Chronosphere Observability Platform enforces two categories of limits that govern how telemetry data flows through the system: license limits and system limits. To stay within defined limits, control your telemetry data to manage data volume.

​
License limits

License limits are defined in your contract and track telemetry usage against your purchased capacity. Licensing applies across metrics, traces, logs, and change events, and is measured by using dimensions such as persisted writes, matched writes, and persisted cardinality. Organizations that purchase credits can spend a single pool of capacity across any telemetry type. Track consumption against your budgets using the License Overview, which surfaces snapshot and trend views per telemetry type. Refer to these pages for terminology about licensing in Observability Platform:
  • Concepts describe licensing concepts across telemetry types.
  • Definitions provide formal definitions of units like credits, persistence, and resolution.

​
System limits

System limits are technical constraints that protect Observability Platform from instability caused by abnormal traffic patterns. For organizations that use consumption pricing, consumption system limits restrict rapid increases in metrics, logs, and traces volume. View the thresholds, utilization, and dropped data for your tenant in the Consumption System Limits dashboard. Consumption system limits apply separately from contract credit consumption and customer-configured budgets. Contact Chronosphere Support to request an adjustment to these limits. Observability Platform also applies data validation, ingestion, and query protections for each telemetry type. See system limits for details.