Join us

ContentUpdates and recent posts about Grafana Tempo..
 Activity
@derynleigh started using tool OWASP Dependency-Check , 2 weeks, 6 days ago.
 Activity
@derynleigh started using tool Amazon S3 , 2 weeks, 6 days ago.
 Activity
@derynleigh started using tool Amazon ELB , 2 weeks, 6 days ago.
 Activity
@derynleigh started using tool Amazon EC2 , 2 weeks, 6 days ago.
 Activity
@derynleigh started using tool Amazon Cloudfront , 2 weeks, 6 days ago.
 Activity
@derynleigh started using tool Akamai , 2 weeks, 6 days ago.
Story
@laura_garcia shared a post, 2 weeks, 6 days ago
Software Developer, RELIANOID

🔐 RELIANOID & NIST Cybersecurity Framework Alignment

At RELIANOID, security is built into both our Load Balancer and our internal operations. We align our product and organizational practices with the NIST Cybersecurity Framework (CSF) across its five core functions: Identify, Protect, Detect, Respond, and Recover. ✔️ Consistent security controls acro..

NIST Cybersecurity Framework RELIANOID compliance
Link
@varbear shared a link, 2 weeks, 6 days ago
FAUN.dev()

Goodbye Microservices

Twilio Segment collapsed 140+ destination-specific microservices into asingle monolith, one repo, one set of dependencies, one test harness. They leveled out version sprawl and builtTraffic Recorder, a homegrown yakbak-based HTTP playback tool. That killed off hours-long test runs, dropping them to.. read more  

Link
@varbear shared a link, 2 weeks, 6 days ago
FAUN.dev()

Why I Didn’t Sign the Resonant Computing Manifesto: The Foundations Need Work

A sharp critique of theResonant Computing Manifestopushes it past vague ideals. It calls for real governance scaffolding, not just poetic prose. Without that? The manifesto risks becoming just another glossy PDF for entrenched players to wave around while changing nothing. Under the hood:What’s real.. read more  

Why I Didn’t Sign the Resonant Computing Manifesto: The Foundations Need Work
Link
@varbear shared a link, 2 weeks, 6 days ago
FAUN.dev()

Rust unit testing: file writing

To test file writes without hitting the disk, the author swaps in a closure that takes a file handle. That handle’s a test double, so after the code runs, you can crack it open and inspect what got written... read more  

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.