Bring every profile type into one workflow
Analyze CPU, memory, and other profile types in Dash0. Use OpenTelemetry to bring profiles from eBPF-based profilers and pprof sources into the same place.
eBPF Continuous Profiling released
Turn your OpenTelemetry profiles into code-level resource insights. Investigate CPU time, memory allocations, and other profile types to find the code paths worth optimizing.
Start for free or Book a demo

Infrastructure engineer - Chargetrip
In an age of overly complex tools, we find that Dash0 stands out for its simplicity and speed. With simple pricing, easy integration, amazing filtering capabilities, fast handling of large data volumes, and straightforward alerting with clear error messages, Dash0 makes observability a breeze.

CTO - Hayuno AG
Despite being a young company, Dash0 delivers enterprise-grade quality and features—automatic instrumentation, spans, logs with semantic context, PromQL support, AI-powered trace triage—all working reliably from day one.

Senior Full-Stack Engineer - catchHR
Dash0 has significantly streamlined our approach to observability and OpenTelemetry, bringing everything together in one place. The intuitive interface and seamless integration have enabled us to quickly gain valuable insights into our systems and resolve issues efficiently.

Senior Web Developer - CroCoder
What I love most about Dash0 is that it's fully OpenTelemetry native which has significantly improved our software development process. The seamless navigation from logs to traces to metrics streamlines bug diagnosis and troubleshooting, enhancing our team's efficiency.

Software Engineer - Vercel
The tracing UI is amazing. When we switched to Dash0, it significantly cut down the amount of time from a bug being reported to figuring out why it happened and fixing it. Filtering on attributes is extremely intuitive, and the tracing tree UI is awesome.

DevOps Cloud Architect - AV Software Solutions 360° at Bechtle
With Dash0, we have found an OpenTelemetry-native solution that provides the flexibility we need. With the support of the open standard OpenTelemetry, we are able to handle public resources responsibly.

Solution Architect - Porsche Digital
Dash0's foundation on open source standards ensures future-proof and next-gen observability. Their focus on ease of use empowers all of our developers to gain insights quickly.
Dash0 supports any profile type delivered through OpenTelemetry, including pprof profiles collected with the OpenTelemetry Collector. Find where your workloads use resources and decide which code to optimize.
Analyze CPU, memory, and other profile types in Dash0. Use OpenTelemetry to bring profiles from eBPF-based profilers and pprof sources into the same place.
See how resource usage is distributed across your call stacks. For CPU profiles, identify the functions taking the most CPU time. With eBPF, follow execution beyond application code into system calls.
Explore the call stacks behind resource usage, focus on the workloads you want to optimize, and follow changes over time. With eBPF-based profiles, see application stack frames and system-call frames together.
Use memory profiles to identify the code paths behind your workload's memory consumption. Inspect Memory In-Use Bytes to see allocations associated with live objects.
Filter profiles to narrow your investigation. For CPU profiles, group consumption by Kubernetes pod to find the biggest consumer, then focus on its series without the noise of the others.
Follow CPU consumption over time to identify spikes and changes in workload behavior. Use the timeline to guide your investigation into the code running at the time.
Compare profiles from two timeframes to see what changed, then focus on a frame to inspect its callers and callees. For CPU investigations, check activity across logical cores to understand how work is distributed.
Compare a baseline with another timeframe to see how resource consumption changes. Use the differential flame graph to find the code paths behind the difference.
Inspect CPU activity by node and logical core. Spot uneven activity and identify the cores to investigate instead of relying on a workload-wide total.
Focus on a stack frame in the Sandwich view to see what calls it and what it calls. Inspect the frame's total and self time, source file, and line number to understand where the work happens.
Explore what's included, how OpenTelemetry-native profiling works, and how to get started.