Review these expected limitations before opening a support case.

Sampling and metrics

Sampled-out traces cannot be recovered by changing retention. Independently generated metrics may still show an aggregate symptom, while metrics derived from sampled spans represent only retained traffic.

Delayed and incomplete traces

Spans can arrive at different times, so a recently opened trace can appear incomplete until export finishes. Short-lived processes must flush completed spans before exit.

Identity changes

Changes to service or operation names create separate entries in searches and metrics. Ephemeral names and raw URL paths also increase cardinality.

Correlation gaps

Trace-log and trace-resource correlation requires shared identifiers or consistent resource attributes. Timestamp proximity alone is not a reliable correlation key.

Feature and version differences

Available widgets, export actions, configuration fields, protocols, and library behavior can vary by deployed version and enabled capability. Consult the compatibility information supplied with your deployment before changing configuration.

For unresolved behavior, provide a sanitized reproduction and confirm whether it persists on a currently supported version.