- 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.
Stay under capacity limits
Chronosphere enforces license 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 to track your telemetry usage against your licensing.
- Review the cardinality dashboards to identify information you can use to help reduce cardinality.
- Query key metrics to understand if Observability Platform is actively dropping data.
- Use the provided tools and techniques to avoid hitting persisted cardinality limits.