> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Observability Platform system limits

Chronosphere sets unchangeable system limits to protect the system from failing in
case of a catastrophic event. These limits are like a circuit breaker that trips to
protect the system in the event of an abnormality in your data traffic patterns, such
as sudden, unexpected spikes in data ingestion.

Learn more about limits and protections for the following data types:

* [Events](/administer/limits-licensing/limits/event-limits): Ingest rate caps and
  field-level validation for change events.
* [Logs](/administer/limits-licensing/limits/log-limits): Maximum individual log size
  and label length constraints.
* [Metrics](/administer/limits-licensing/limits/metric-limits): Label size, label
  count, total series byte limits, and late- or future-arriving data windows.
* [Queries](/administer/limits-licensing/limits/query-limits): Per-query scale
  protections, browser truncation limits, resource balancing, and automated source
  rate limits.
* [Traces](/administer/limits-licensing/limits/trace-limits): Tag size, span timing
  validity, trace span count, and per-pod ingest caps.

## Stay under capacity limits

Chronosphere enforces [license capacity limits](/administer/limits-licensing/concepts/capacity-licensing#capacity-limits)
for all of your telemetry data. Exceeding these limits can put your organization at
the 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:

* Use the [License overview](/administer/limits-licensing/licensing) to track your
  telemetry usage against your licensing.
* Review the
  [cardinality dashboards](/observe/dashboards/managed-dashboards#cardinality-dashboards)
  to identify information you can use to help reduce cardinality.
* Query [key metrics](/administer/limits-licensing/concepts/capacity-licensing#capacity-limits) to understand
  if Observability Platform is actively dropping data.
* Use the provided tools and techniques to
  [avoid hitting persisted cardinality limits](/administer/limits-licensing/concepts/capacity-licensing#avoid-persisted-cardinality-limits).