Tracing ingest limits

Chronosphere uses the following ingest limits for tracing data. If you exceed one or more of these limits, Chronosphere truncates or rejects the data depending on the limit itself. Exceeding a limit indicates that you might need to modify your client-side instrumentation, or implement head or tail sampling rules to drop data that you don't want to persist.

The following limits are in increasing order of granularity from most granular to most broad.

Tag limits

Chronosphere limits the size of a tag to 200 bytes for any span. Chronosphere accepts and processes the first 200 bytes and truncates any additional bytes. The related span and trace aren't otherwise impacted by this limit.

Span limits

If the start time of a span is greater than 10 minutes before or after the current time, Chronosphere marks the span as invalid and drops it. The parent trace isn't impacted, provided that the other spans in the trace have valid start times.

Trace limits

Chronosphere persists individual traces with 100,000 spans or fewer. If a trace has more than 100,000 spans, Chronosphere rejects the trace and all included spans.

Pod limits

Chronosphere limits data ingest to 2 GB per minute for each Kubernetes pod that handles data ingest. Chronosphere scales these pods automatically to handle current traffic, and imposes this limit to protect against sudden traffic surges to a single pod. Your tenant might have anywhere from two to 100 pods at any given time, depending on current load. The total ingest limit in one minute depends on the number of pods in use times the 2 GB per minute for each pod.