Michele Mancioppi

Michele Mancioppi

@michele.dash0.com

Chief Architect & Head of Open Source and Community @Dash0. Unrepentant observability nerd. Observability, Animated!

138 followers155 following248 posts

View full thread

Well yes, but not by itself: as of v0.161.0, the intervalprocessor aggregates only cumulative temporality and passes delta through unchanged. This caught me by surprise (and not just once either...).

Instead you need three components in a row: deltatocumulative to convert, intervalprocessor to drop the cumulative data points you do not want to keep, and cumulativetodelta to convert back.

View full thread

For delta temporality, aggregation is *much* *more* *interesting*. In the OpenTelemetry Collector there is the intervalprocessor, which sounds like the correct tool for the job, right?

View full thread

Summaries do not carry temporality either, since their count and sum are always cumulative. And speaking of summaries: they are an aberration you should never ever use, because their quantiles cannot be merged.

For cumulative temporality, temporal aggregation is a bit like sampling in traces: you throw away the data points you do not want to keep. And since the data points that remain are self-contained, you are pretty much done.

View full thread

Cumulative temporality means that each data point is effectively self-sufficient, as it contains the entire value; in Prometheus, counters are always cumulative. Delta temporality is a client-side optimization that represents only the change since the last export (hence "delta").

Temporality is a property of the metric, not of the individual data point: sums, histograms and exponential histograms have temporality. Gauges do not, because points you cannot combine have no aggregation to be cumulative or delta about.

View full thread

How you perform the aggregation fundamentally depends on two things: what type of data points you want to aggregate, and their *temporality*. In OpenTelemetry there are two temporalities: #cumulative and #delta.

View full thread

#SpatialAggregation is about merging timeseries: usually you want to throw away some attributes (a.k.a. "labels" in Prometheus) on the data points to reduce #cardinality.

The identity of a timeseries is its set of attributes and their values, so removing attributes merges timeseries. That leaves several data points at more or less the same timestamp, which need to get merged into one.

#TemporalAggregation is when you reduce the number of data points of a timeseries, increasing the interval between subsequent ones. That is: you make the timeseries less "dense".

Let's talk about #Trace #sampling, how it allows you to harness the power of distributed tracing without breaking the bank, how it adds inaccuracies, and how you fix that. 🧵

View full thread

Let's talk about #Trace #sampling, how it allows you to harness the power of distributed tracing without breaking the bank, how it adds inaccuracies, and how you fix that. 🧵

View full thread

Head and tail sampling reduce the accuracy of your data, over or underestimating error rates and latencies of your services. (Btw, creating animations with LLMs is pretty addictive.)

What can you do to reduce inaccuracies? You additionally record rate, errors and durations (RED) metrics for your services on the full data before sampling. With #OpenTelemetry, you can do trace sampling and RED metrics collection inside the same Collector.

Let's talk about #Trace #sampling, how it allows you to harness the power of distributed tracing without breaking the bank, how it adds inaccuracies, and how you fix that. 🧵

There are two commonplace ways of doing sampling: probabilistic head sampling and tail sampling. With probabilistic head sampling, it is like you throw a die for every trace, and keep it only if the die's face is low enough. With tail sampling, you keep *interesting* traces.

Hello BlueSky! On Monday I am starting a long-running series of threads called #Observability #Animated, in which we dive deep into advanced observability and #OpenTelemetry concepts.

For the first few weeks it is going to be almost daily (I have a good amount of content prepared!) then twice a week. Let me know if you have burning questions or curiosities about #O11y or #OpenTelemetry ;-)

Michele Mancioppi reposted

New year resolution: Connect with the #OpenTelemetry community IRL ✨ OTel Unplugged EU - Feb 2 in Brussels → Unconference format → You pick the topics → Direct maintainer access → Real roadmap influence 1 month out. Limited spots: buff.ly/aaUyQsx RT if you're attending or thinking about it!

Michele Mancioppi reposted

Last day of #KubeConNA 2025! 🎨 Meet The Artist, the final (but not least!) Agent0 MtG card celebrating the launch of Agent0. In Dash0, The Artist builds and maintains dashboards and alert rules for you. In MtG, it creates and buffs constructs to help you win. Find The Artist at Booth 710!

Come and see what we cooked up! #Observability #MagicTheGathering #OpenTelemetry

Dash0@dash0.com

Hello Internet! Ready for KubeCon? 🔥 To celebrate last week’s launch of #Agent0 - the integrated Agentic #AI inside #Dash0 - we made something we’re pretty stoked about. At #KubeConNA 2025, we’re giving away five custom MtG-style cards. Find us at booth 710 - first teaser: The Seeker & The Oracle!

Michele Mancioppi reposted

If you are in Berlin next week and would like to catch up, ping me on DMs :-)

Dash0@dash0.com

The Dash0 crew is getting ready to reunite for #WeAreDevelopers 2025 in Berlin, and excited to show Dash0 in action! 🇩🇪 Don’t miss our CEO Mirko on July 11, on the Tech Leaders Stage, joining a panel about the AI-Ready Stack. It all kicks off next week. Book a live demo: dash0.link/WeAreDevelop...

Michele Mancioppi reposted

🚨 On-call chaos? Alerts blowing up? Dashboards, DMs, and confusion everywhere? We’ve all been there. That’s why we’re excited to launch our new integration with ilert — making incident response faster, cleaner, and way less stressful. 👉 Check out the integration: s.dash0.com/-ilert

Michele Mancioppi reposted

The Vercel Marketplace adds new integrations from Sentry, Checkly, and Dash0. Use the tools you already trust to monitor, measure, and debug your apps. • Integrated billing • SSO access to provider dashboards • Log Drains from supported providers vercel.com/blog/expandi...

vercel.comExpanding observability on Vercel - VercelThe Vercel Marketplace adds new native integrations from Sentry, Checkly, and Dash0. Use the tools you already trust to monitor, measure, and debug your apps with integrated billing, single sign-on, a...