The #observability work that sticks is rarely dramatic. Most of the time, it’s calibration.
In Code RED #26, @kaspernissen.xyz looks at smarter sampling, Collector resilience, and the evolving Prometheus + #OpenTelemetry relationship.
Check it out 👉 dash0.link/newsletter-26
Back-to-back events lately: Brooklyn Tech Expo, Container Days, and DeveloperWeek.
What stuck with us wasn’t just the talks or booth time, but the conversations. Teams sharing what’s actually hard: messy telemetry, growing complexity, and making #OpenTelemetry scale.
Next stop: #KubeCon Amsterdam
What does #observability look like under pressure? We’re about to find out.
We’re hosting Hotservability, a live interview inspired by the Hot Ones show, where the questions get deeper as the sauces get hotter 🔥
Booth 760 · Mar 24 · 17:30
Register for the prize draw: dash0.link/hotservabili...
Raw #telemetry is noisy. Making it usable is the foundation of effective observability.
Our latest guide breaks down how to use the #OpenTelemetry Transform Processor correctly, from parsing and #OTTL to error modes and avoiding silent data loss.
Full guide here: dash0.link/otel-transfo...
Agentic observability has great potential, but how do you get started?
On March 18, Michele Mancioppi joins a LeadDev panel on what needs to be in place for agentic #AI to pay off: data management, #OpenTelemetry, effective #telemetry, and guardrails.
Register here: dash0.link/leaddev-a-bl...
What if observability wasn’t about reacting faster, but preventing outages?
In Code RED, Mirko Novakovic talks with Aaron “Checo” Pacheco about why #observability still feels reactive, the myth of a “single pane of glass,” unused telemetry, and the shift toward prevention.
🎧 dash0.link/podcast-37
Meet the Lookout Agent: AI for #WebPerformance
Stop writing queries. Start asking questions.
“Top errors today?” “Which pages have poor Core Web Vitals?” “Show abandoned checkout.”
Get answers from your #observability data with AI built for #frontend performance.
👉 dash0.link/the-lookout-...
You’re deep in a trace. Sunlight hits your screen.
That’s where Light Mode comes in.
From Service Map to complex trace views, Dash0 adapts to brighter workspaces while keeping hierarchy and critical signals clear.
Switch anytime, or let it follow your system.
👉 dash0.link/light-mode
In a month, #KubeCon kicks off in Amsterdam.
Once it starts, all that planning turns into real conversations about #OpenTelemetry, architecture, trade-offs, and what’s breaking in production.
Find us at Booth #760 in the red jumpsuits. You won’t miss us.
Observability shouldn’t cost you user privacy.
Stop sending auth tokens and PII to your backend. We break down how to use #OpenTelemetry Collector processors to redact sensitive data:
Keep your signals, lose the compliance risk.
Read more: www.dash0.com/guides/scrub...
Once #telemetry is flowing, the real question is how to keep it usable.
Code RED #25 by @kaspernissen.xyz looks at that layer of #observability, from log deduplication and pipeline hygiene to keeping signals structured enough to reason about.
Read here 👉 dash0.link/code-red-25
If pricing needs a calculator, it’s probably too complicated.
Ours doesn’t.
Metrics: $0.20 per million
Logs & Spans: $0.60 per million
That’s it.
👉 dash0.link/dash0-pricing
#Dash0 #SimplicityWins
Many teams treat observability as a tooling choice.
In reality, it’s about asking and answering the right questions quickly during an incident.
Our latest article breaks down when logs make sense, when tracing gives faster answers, and how #OpenTelemetry connects them.
👉 dash0.link/traces-vs-logs
In large projects like #OpenTelemetry, getting your first PR reviewed involves more than just the code.
In Code RED, @kaspernissen.xyz talks with Marylia Gutierrez about what influences reviews at scale, why they can take time, and how contributors grow into maintainers.
🎧 dash0.link/podcast-36
In distributed systems, one missing trace header can fragment a trace into disconnected spans.
That’s why #ContextPropagation matters, and why #W3CTraceContext defines the standard.
We break down traceparent, tracestate, and how #OpenTelemetry propagates context.
👉 dash0.link/w3c-trace-co...
Last week, we announced the Dash0 + Lumigo acquisition.
Since then, conversations have centered on what changes and what doesn’t.
They’ve focused on what this means for observability workflows, migration, licensing, timelines, and AWS-native/serverless teams.
Full context: dash0.link/dash0-lumigo
Applications don’t start as black boxes. They become black boxes the moment something breaks, and nobody can explain why.
At DeveloperWeek, Julia Morgado and Vitor Mouzinho show how to turn them into glass boxes using telemetry, traces, metrics, and logs.
Workshop: Feb 20
See it live at Booth #528
Many teams still rely on a few “power users” who hold system context in their heads.
Mirko Novakovic joined Guy Podjarny to discuss why that model concentrates knowledge, and how #OpenTelemetry and #AI agents can make system context more accessible across teams.
Watch: dash0.link/the-ai-nativ...
Async workflows are great for building systems.
Observing them end-to-end is hard.
At #ContainerDays London, @kaspernissen.xyz and Mauricio Salatino show how teams keep distributed workflows observable with #Dapr + #OpenTelemetry - when systems stop being linear.
You will also find us at Booth A6👋
Stop paying to store the same error 10,000 times.
The #OpenTelemetry logdedup processor collapses log storms into single records to cut storage bloat, while preserving context and frequency.
It’s a fast way to lower #observability costs without losing visibility.
👉 dash0.link/otel-log-ded...
What’s happening across the #OpenTelemetry ecosystem lately?
Code RED #24 tracks the latest community signals: from early #observability blueprints and support maturity proposals to real-world OTel Collector feedback and updates from OTel Unplugged.
Dive into the details 👉 dash0.link/newsletter-24
Dash0 is kicking off the event season at Brooklyn Tech Expo next week.
Julia Morgado will be on stage, talking about how #AI changes the way teams build software - and why #observability becomes essential when systems get harder to understand.
👉 pulse.nyc/brooklyn-tec...
Come say hi at Booth #17.
Dash0 has acquired Lumigo 🚀
#Lumigo brings deep expertise where #observability gets hard: serverless systems and #AWS-native environments.
This means stronger serverless observability, first-class support for AWS-managed services, and Lumigo’s Copilot capabilities!
👉 dash0.link/dash0-acquir...
Still using the #OpenTelemetry Batch Processor?
In-memory buffering can mean 100% data loss.
The community now favors exporter-level batching for better durability. Julia breaks down why #observability and #CloudNative teams are making the switch:
👉 dash0.link/the-otel-bat...
The OTLP HTTP exporter is the boundary against data loss.
To build a resilient #observability pipeline, you need to tune persistence and backoff.
We explain how to configure #OpenTelemetry so a simple network blip doesn’t turn into an #SRE incident.
Full deep dive 👉 dash0.link/otel-otlp-ht...
"Why is the site slow?" hits differently when metrics look fine, but users are still frustrated.
Julia’s new guide on #WebsiteMonitoring shows how #OpenTelemetry + Dash0 make #RUM visible - so you can see the full story of real user behavior.
Read it here: dash0.link/website-moni...
Aakansha Priya is back on stage this Thursday, speaking about managing #OpenTelemetry at scale.
Hundreds of collectors across #clouds, edges, and on-prem.
Manual per-host management. Config drift.
This is where #OpAMP comes in.
Full details here: ndclondon.com/agenda/opent...
What happens when AI agents want direct access to #observability data?
Mirko Novakovic and Spiros Economakis discuss whether vendors will restrict access or build native #AI agents like Agent0.
As token prices rise, data-layer efficiency becomes critical for #DevOps.
🎧 dash0.link/35-code-red
Logs alone can’t explain how a request moves across microservice boundaries.
We published a deep dive into #DistributedTracing mechanics, why spans without attributes are just stopwatches, and why context propagation is the hardest part of #OpenTelemetry.
Read more here: dash0.link/distributed-...
#OpenTelemetry is in its operations era.
2026 is about running it day-to-day without losing signal.
New Code RED from @kaspernissen.xyz: 10k Slack messages on where #observability teams get stuck, plus OTel governance and the real SRE bottleneck: operational maturity.
👉 dash0.link/code-red-new...
