Join us

ContentUpdates and recent posts about Grafana Tempo..
Story
@viktoriiagolovtseva shared a post, 1 week, 1 day ago

Vendor Payment Template for Jira

Vendor Payments Take Too Much Time And There Is a Way Out of the Vicious Cycle

Zrzut ekranu 2026-01-02 142203
 Activity
@virk started using tool Node.js , 1 week, 3 days ago.
 Activity
@virk started using tool AdonisJS , 1 week, 3 days ago.
Story Trending
@laura_garcia shared a post, 1 week, 3 days ago
Software Developer, RELIANOID

✨ Thank You, 2025 — What a Year for RELIANOID! ✨

As the year comes to a close, we want to take a moment to look back and saythank youto everyone who has been part of RELIANOID’s journey in 2025. This year has been all aboutgrowth, innovation, and community: 🚀Product & Technology - Continued evolution ofRELIANOID Enterprise Edition, delivering high..

carrusel1
Story Trending
@laura_garcia shared a post, 1 week, 4 days ago
Software Developer, RELIANOID

AI-driven cyberthreats are reshaping industrial security faster than many manufacturers expect.

As we approach 2026, attackers are already leveraging AI to automate reconnaissance, social engineering and intrusion workflows—often at machine speed. For manufacturing environments, where IT and OT increasingly converge, this creates a new risk landscape. In our latest article, we explore: - Why A..

Blog Manufacturing industry cyberthreats previsions 2026 RELIANOID
Story Trending
@viktoriiagolovtseva shared a post, 1 week, 4 days ago

Your Guide to Cloning in JIRA: How to Clone Issues in Different Ways

While cloning in Jira can be done in just a few clicks, it becomes less straightforward when you have special requirements. What if you need to clone an issue to a different project, clone tasks in bulk, or do this automatically on a schedule? In this article, we explore all these scenarios and provide you with examples and step-by-step instructions.

Zrzut ekranu 2025-12-30 142435
 Activity
@ilobe started using tool Snyk , 1 week, 4 days ago.
 Activity
@ilobe started using tool Weights & Biases , 1 week, 4 days ago.
 Activity
@ilobe started using tool Azure , 1 week, 4 days ago.
 Activity
@ilobe started using tool Amazon Web Services , 1 week, 4 days ago.
Grafana Tempo is a distributed tracing backend built for massive scale and low operational overhead. Unlike traditional tracing systems that depend on complex databases, Tempo uses object storage—such as S3, GCS, or Azure Blob Storage—to store trace data, making it highly cost-effective and resilient. Tempo is part of the Grafana observability stack and integrates natively with Grafana, Prometheus, and Loki, enabling unified visualization and correlation across metrics, logs, and traces.

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.