Join us

ContentUpdates and recent posts about Grafana Tempo..
Link
@kala shared a link, 2 months ago
FAUN.dev()

Streamlining Security Investigations with Agents

Slack broke down how it's threading AI into its product without torching user trust.Slack AIleans hard ontenant-specific data isolationandzero data retention- no leftover crumbs from LLM interactions. Instead of piping user data through someone else’s APIs, Slack runs LLMs onits own infrawhere it ca.. read more  

Streamlining Security Investigations with Agents
Link
@kala shared a link, 2 months ago
FAUN.dev()

2025: The year in LLMs

2025 was the year LLMs stopped just answering questions and started building things.Reasoning modelslike OpenAI’s o-series and Claude Code took over tool-driven workflows. Asynchronous coding agentsbroke out. These models didn’t just write code - they ran it, debugged it, then did it again. That loo.. read more  

2025: The year in LLMs
Link
@kala shared a link, 2 months ago
FAUN.dev()

Meet the ‘Mad Max’-Loving CEO Challenging Nvidia With a Renegade Chip

June Paik spurned a takeover offer from Meta Platforms last year. Now his South Korean company, FuriosaAI, has an AI chip entering mass production... read more  

Link
@kala shared a link, 2 months ago
FAUN.dev()

The Architects of AI Are TIME's 2025 Person of the Year

The Architects of AI drove the economy, shaped geopolitics, and changed the way we interact with the world... read more  

The Architects of AI Are TIME's 2025 Person of the Year
Link
@kala shared a link, 2 months ago
FAUN.dev()

My LLM coding workflow going into 2026

Anthropic saysClaude Code writes about 90% of its own code now. Why? Because devs are getting smart with AI. They're slicing problems into tight, testable chunks and running structured workflows that keep LLMs on a short leash. It's not just prompts anymore. Think context packaging, multi-agent setu.. read more  

My LLM coding workflow going into 2026
Link
@devopslinks shared a link, 2 months ago
FAUN.dev()

Race Condition in DynamoDB DNS System: Analyzing the AWS US-EAST-1 Outage

A long AWS smackdown in US-EAST-1 traced back to a ticking time bomb inDynamoDB’s automated DNS system. The flaw torpedoed EC2 networking, hobbled Lambda and Fargate, and dragged down theNetwork Load Balancer. Endpoints ghosted. Configs stalled. Everything snowballed. AWS says they’ll upgrade EC2 th.. read more  

Race Condition in DynamoDB DNS System: Analyzing the AWS US-EAST-1 Outage
Link
@devopslinks shared a link, 2 months ago
FAUN.dev()

You don’t need NAT gateway to deploy Lambda into VPC

AWS just made a big dent in NAT gateway bills. You can now runLambda in VPCs with IPv6 and an egress-only Internet gateway- no more always-on NAT draining your wallet. Keep the private subnets locked down. Still get outbound Internet access. IPv6 handles the traffic, slicing out the NAT middleman... read more  

You don’t need NAT gateway to deploy Lambda into VPC
Link
@devopslinks shared a link, 2 months ago
FAUN.dev()

Designing a Scalable Serverless Contact System with AWS and Terraform

TravelEase Inc., a growing travel company, significantly improved customer inquiries handling by replacing a basic mailto: link with a modular, serverless, cloud-native system managed with Terraform. This new system automated message validation, processing, storage, and notifications using Lambda fu.. read more  

Link
@devopslinks shared a link, 2 months ago
FAUN.dev()

Datacenters in space are a terrible, horrible, no good idea.

A former NASA engineer - now a Google Cloud AI infra alum - rips apart the idea of building GPU datacenters in orbit. His verdict: space is a terrible server rack. Power delivery? A nightmare. Heat dissipation? Worse in a vacuum. Radiation? Frying time. Even a 200kW solar rig (think ISS-sized) could.. read more  

Datacenters in space are a terrible, horrible, no good idea.
Link
@devopslinks shared a link, 2 months ago
FAUN.dev()

ArgoCD diffs at scale

Monday.com ditched ArgoCD's built-in manifest diffing. Instead, they wired up a custom CI renderer that pre-renders Helm charts using real cluster data. Then it compares the desired states across Git branches. The kicker: diffs go to a UI with custom grouping support. Reviews get easier. New devs ge.. read more  

ArgoCD diffs at scale
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.