Activity
@pixel_og started using tool Kubernetes , 1 week, 2 days ago.
Activity
@pixel_og started using tool Google Kubernetes Engine (GKE) , 1 week, 2 days ago.
Activity
@pixel_og started using tool Google Cloud Platform , 1 week, 2 days ago.
Activity
@tairascott gave 🐾 to Helm 4 or Nelm? What's the difference , 1 week, 3 days ago.
Activity
@tairascott gave 🐾 to Hidden Correlations Traditional Monitoring Misses , 1 week, 3 days ago.
Technically, Tempo supports ingestion from major tracing protocols including Jaeger, Zipkin, OpenCensus, and OpenTelemetry, ensuring easy interoperability. It features TraceQL, a domain-specific query language for traces inspired by PromQL and LogQL, allowing developers to perform targeted searches and complex trace-based analytics. The newer TraceQL Metrics capability even lets users derive metrics directly from trace data, bridging the gap between tracing and performance analysis.
Tempo’s Traces Drilldown UI further enhances usability by providing intuitive, queryless analysis of latency, errors, and performance bottlenecks. Combined with the tempo-cli and tempo-vulture tools, it delivers a full suite for trace collection, verification, and debugging.
Built in Go and following OpenTelemetry standards, Grafana Tempo is ideal for organizations seeking scalable, vendor-neutral distributed tracing to power observability at cloud scale.



