OpenTelemetry21h ago

The #OpenTelemetry website and documentation SIG is taking a look back at 2025:

- Eight localization teams produced nearly 75k lines of translation! 🚀
- PRs merged grew 50%! 📈
- Ten contributors were promoted to SIG leadership! 🔟

Looking to get started in open source? Documentation is a great entry point! Check out our new blog post for all the exciting achievements from last year and how you can join us this year.

https://opentelemetry.io/blog/2026/2025-year-in-review/

Rui Carmo1d ago

I need to stop reinventing wheels - but hey, the icon is really cute! #opentelemetry #graphite #golang

https://github.com/rcarmo/gotel

GitHub - rcarmo/gotel: OpenTelemetry for... tiny gophers

OpenTelemetry for... tiny gophers. Contribute to rcarmo/gotel development by creating an account on GitHub.

GitHub
Show threadVictoriaMetrics2d ago
#OpenTelemetry has become the standard for data collection, but it still depends on a backend capable of handling all three signals efficiently.
Watch now 👇
https://bit.ly/4qbJtck
#Monitoring
Cloud Native Valencia Meetup #3 - Year-end Lightning Talks + cTENcf Party 🎉

YouTube
VictoriaMetrics2d ago
Our Developer Advocate, @dianatodea, presented at Cloud Native Days Valencia, her talk titled “#OpenSource Cloud-Native #Observability with #VictoriaMetrics and #OpenTelemetry.” In #cloud-native environments, understanding the behavior of distributed applications requires complete observability across metrics, logs, and traces.
Rui Carmo2d ago

Any small scale OSS #opentelemetry servers that can be self-hosted/used for local development? Asking for a friend.

(If nothing, then I’ll probably hack something atop #graphite)

OpenTelemetry2d ago

❓ A question to start the year: what can you learn from analyzing thousands of Slack messages?

The #OpenTelemetry project answers this question in our first blog post of 2026. Using a combination of sentiment analysis, frustration indicators, and topic correlation of aggregated Slack data, we identified the top challenges for #OTel users. We'll be working to address these issues over the course of the year. Come join us!

https://opentelemetry.io/blog/2026/slack-community-insights/

Show threadVictoriaMetrics3d ago
You’ll gain practical insights on:
🔹 How #VictoriaMetrics and #VictoriaLogs help unify your observability signals (with a Grafana demo)
🔹 #OpenTelemetry — benefits, common pitfalls, and certification tips
🔹 The difference between #SRE and Platform Engineering
https://www.youtube.com/live/E9t3aLkR6js
#Observability #PodcastTech
eAfterWork EP 10: Observabilité illimitée + OpenTelemetry sur une stack open source w/ DIANA TODEA

YouTube
Aaron Lord 3d ago
Another #OpenTelemetry question. Even when using `getWebAutoInstrumentations()` I am not getting any correlation between clicks and the subsequent API calls. I'm using #React and everything is asynchronous. But I'm wrapping this particular API with `context.with(context.active(), () => {` and it still doesn't work.
OpenTelemetry3d ago
New year resolution: Actually 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: https://events.humanitix.com/otelunplugged-eu2026
RT if you're attending or thinking about it! 🔄
Show threadAaron Lord 5d ago
@dmathieu thanks for showing me the way! I've implemented a custom OnlyErrorsTraceExporter which takes the input spans and groups them by trace Id and passes them to the member otlp exporter only if there is an error in the trace. The new question is whether the member otlpTraceExporter is going to fill up memory with unexported spans or if that is handled by the calling BatchSpanExporter.
#OpenTelemetry