Dash0
banner
dash0.com
Dash0
@dash0.com
OpenTelemetry-Native Observability.

Because details matter.
No lock-in.
No surprises.
No hassle.

www.dash0.com
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
February 13, 2026 at 3:24 PM
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
February 12, 2026 at 1:56 PM
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...
February 11, 2026 at 5:33 PM
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👋
February 10, 2026 at 1:59 PM
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...
February 9, 2026 at 2:36 PM
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
February 6, 2026 at 1:23 PM
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.
February 5, 2026 at 1:40 PM
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...
Dash0 Acquires Lumigo to Expand Agentic Observability Across AWS and Serverless · Dash0
Acquisition brings deep AWS-native observability expertise, LLM visibility, and AI-powered operations to Dash0’s OpenTelemetry-first platform.
dash0.link
February 4, 2026 at 2:31 PM
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...
Why the OpenTelemetry Batch Processor is Going Away (Eventually) · Dash0
An analysis of why the OpenTelemetry community is moving away from the in-memory batch processor in favor of exporter-level batching. This post explains the architectural limitations of memory bufferi...
dash0.link
February 3, 2026 at 2:19 PM
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...
Mastering the OpenTelemetry OTLP HTTP Exporter · Dash0
Learn how to configure and optimize the OTLP HTTP exporter for secure reliable and scalable telemetry delivery
dash0.link
February 2, 2026 at 1:50 PM
"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...
January 29, 2026 at 1:11 PM
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...
January 28, 2026 at 1:23 PM
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
#35 - Preventing the Next Outage: How NOFire Uses Causal and Agentic AI to Shift Reliability Left with Spiros Economakis · Podcast · Dash0
NOFire AI founder and CEO Spiros Economakis joins Dash0’s Mirko Novakovic to discuss why traditional observability and post-incident RCA are no longer enough in an AI-accelerated engineering world.
dash0.link
January 27, 2026 at 1:24 PM
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-...
January 26, 2026 at 1:29 PM
#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...
January 23, 2026 at 1:22 PM
Dash0 keeps growing - and so does our amazing team around the world.

In just a few months, this group didn’t just scale - it clicked.
Ideas get challenged, details get sharpened, and real progress happens fast.

Hvala to the Novi Sad team 🇷🇸
January 22, 2026 at 1:38 PM
Migrating from #Fluentd to the OpenTelemetry Collector?

Fluentd buffers to disk. The Collector defaults to memory - so a pod restart can mean lost #logging data.

Here’s how to configure #OpenTelemetry persistent queues safely.

👉 dash0.link/otel-fluent-...
January 21, 2026 at 1:24 PM
Ever looked at a distributed trace that felt incomplete?

The async workflow in between often breaks the trace.

@kaspernissen.xyz teamed up with Mauricio Salatino to show how #Dapr Workflows can keep a single, end-to-end trace using #OpenTelemetry.

👉 dash0.link/dapr-workflo...
Deep Diving into Dapr Workflows and OpenTelemetry – Tracing the Invisible Parts of Asynchronous Communication · Dash0
Tracing asynchronous workflows is one of the hardest observability problems to solve. In this post, we dive deep into how Dapr Workflows actually execute, why distributed tracing breaks across long-li...
dash0.link
January 20, 2026 at 1:44 PM
Still treating logs like simple strings?

With #OpenTelemetry, existing logs are represented as structured events and correlated with traces through automatic context propagation.

A more usable #logging and #observability strategy starts here:

dash0.link/-otel-loggin...
OpenTelemetry Logging Explained: Concepts and Data Model · Dash0
A clear explanation of OpenTelemetry logging including the data model log bridges trace correlation and the role of the Collector
dash0.link
January 19, 2026 at 1:28 PM
It’s all fun and games until your #observability agent actually triggers the outage 😅

Shahar Azulay joins Code RED to unpack observability economics, #eBPF adoption, and pricing incentives.

Plus, how #AI is reshaping the next generation of workflows.

👉 open.spotify.com/episode/3nYH...
January 16, 2026 at 1:19 PM
For years, #observability has promised smarter alerts.
Most teams are still dealing with noise.

On Jan 27, Michele Mancioppi (Dash0) joins Thomas Johnson and Amy Tobey for a #LeadDev panel on what #agentic observability actually looks like today.

📅 Jan 27 · 17:00 GMT
👉 dash0.link/are-you-read...
January 15, 2026 at 1:45 PM
Some “#AI for #SRE” tools ask you to trust their answers without showing how they were produced.

#Agent0 takes a different approach: every conclusion is inspectable, not just the summary.

See how it works in practice → dash0.link/-ai-sre-agent
Agent0 AI for SREs: 5 Capabilities That Matter · Dash0
Learn how to speed up root cause analysis, master PromQL, and generate dashboards as code with Agent0, the AI SRE agent from Dash0
dash0.link
January 14, 2026 at 1:45 PM
If OpenTelemetry has gone from
“we should use this” to “do we actually understand what we’re seeing?”

You’re not alone.

Next week, Orlin Vasilev and Julia Furst Morgado unpack what #observability really looks like with #OpenTelemetry - no deep prior knowledge required.

🔗 dash0.link/rancher-live
RancherLive: OTel me about Observability
Orlin Vasilev will be joined by Julia Furst Morgado (Dash0) as we dive into the world of observability through the lens of OpenTelemetry (OTel). In this sess...
dash0.link
January 13, 2026 at 1:13 PM
Few aspects of logging cause more confusion and debate than severity levels.

Is a retried database connection a WARN, or just normal behavior?

We’ve published a practical framework for using severity levels consistently with #OpenTelemetry, across teams and languages.

👉 dash0.link/log-levels
January 12, 2026 at 2:04 PM
We’re kicking off #2026 on the road.

Here’s where you’ll find the Dash0 team in Q1:

#OtelUnplugged, Brussels, Feb 2
#BrooklynTechExpo, New York, Feb 11
#ContainerDays, London, Feb 11-12
#DeveloperWeek, San Jose, Feb 18-20
#KubeCon, Amsterdam, Mar 23-26
#SREconNA, Seattle, Mar 24-26

Come say hi!
January 9, 2026 at 1:12 PM