Every industry has unique telemetry challenges — from PII in traces to 100K-collector deployments. We’ve talked to dozens of teams to understand what matters most and built tools that improve telemetry quality at the source.
From the field
Enterprise software · North America · Anonymized, but real · Audio episode
One background worker named cli made 45% of all spans, a third of logs were exact duplicates, a third were access logs, and the Collector shipped its own logs again.
Digital health · Europe · Anonymized, but real · Audio episode
Personal data in 1 in 6 services traced to one ORM logging setting, logs with no severity at all, one worker writing most of the logs, and auth tokens Rose found in a day.
Enterprise software · Latin America · Anonymized, but real · Audio episode
Repeated logs, metrics that never change, and a pipeline complaining about itself. How replay-verified Collector changes beat a six-week proof of value, and what happened after.
The findings in these stories fall into five dimensions of telemetry quality: identity, volume and waste, cost drivers, safety, and correctness. What is telemetry quality? →
