Updates and recent posts about Grafana Tempo..

Posts
Description

Activity

@work4bots started using tool Spring , 2 weeks, 3 days ago.

Activity

@work4bots started using tool Helm , 2 weeks, 3 days ago.

Activity

@work4bots started using tool Azure Pipelines , 2 weeks, 3 days ago.

Activity

@work4bots started using tool Azure Kubernetes Service (AKS) , 2 weeks, 3 days ago.

Activity

@work4bots started using tool Azure , 2 weeks, 3 days ago.

Activity

@work4bots added a new tool Bicep , 2 weeks, 3 days ago.

Story FAUN.dev() Team

@eon01 shared a post, 2 weeks, 3 days ago

Founder, FAUN.dev

AWX in Action is out, and there's a course

#red hat... #ansible #Tower #AWX

"AWX in Action: Ansible Orchestration at Scale" is now available in print and ebook. It covers running AWX on Kubernetes for real, not a sandbox demo that falls over the moment you add a second execution node.

Link

@varbear shared a link, 2 weeks, 3 days ago

FAUN.dev()

GitHub breach: The development ecosystem is in the hot seat

GitHub is reeling from an infrastructure breach by TeamPCP, highlighting the vulnerability of developer environments. Privileged access was achieved not through traditional perimeter exploitation, but by targeting trusted developer tools like IDE extensions. This incident serves as a stark reminder .. read more

Link

@varbear shared a link, 2 weeks, 3 days ago

FAUN.dev()

When Code Becomes Cheap, What's Left?

Teams that use Claude Opus 4.6 for spec-driven development generate code at low cost, so they spend scarce developer time on review and QA. Developers create more value by judging code than by typing it... read more

Link

@varbear shared a link, 2 weeks, 3 days ago

FAUN.dev()

Design Patterns Are Dead. Long Live Design Patterns.

Design patterns were created for human comprehension, not machines, serving as a shared vocabulary to communicate complex ideas quickly, manage working memory, and standardize solutions. Even in the era of AI-generated code, design patterns are crucial for containing the limitations of AI models and.. 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.