Q: A tracing backend becomes expensive and slow because span names include full URLs like `/users/123/orders/987`. What is the problem and how do you fix it?
The span name contains unbounded identifiers. Every user ID and order ID creates a different operation name, making search, aggregation, and storage expensive.
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Our SRE team tackled this monitoring and metrics bottleneck to eliminate false-positive alert fatigue. The interviewer is testing: Span naming, high-cardinality trace attributes.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
The span name contains unbounded identifiers. Every user ID and order ID creates a different operation name, making search, aggregation, and storage expensive. I would normalize span names: Then I would store IDs only as attributes if they are safe and necessary, and avoid indexing high-cardinality attributes by default. Good span names represent the operation shape, not one specific request. This lets the tracing backend group latency, errors, and throughput by endpoint correctly.
Bad: GET /users/123/orders/987
Good: GET /users/{user_id}/orders/{order_id}
- Immediate Triage: The span name contains unbounded identifiers. Every user ID and order ID creates a different op
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability tracing backend High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability tracing backend Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability tracing backend Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability tracing backend Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.