I'm sure someone already made this joke, but Rust missed an opportunity in defining their API here:
enum Cow<'a, Bunga> { ... }
12.12.2025 19:20
👍 2
🔁 0
💬 1
📌 0
I'm sure someone already made this joke, but Rust missed an opportunity in defining their API here:
enum Cow<'a, Bunga> { ... }
A blog about (some of) what we've been doing in #OpenTelemery: opentelemetry.io/blog/2025/ot...
This was one of our favorite games since the Kickstarter delivered! Hope you expand it more
PSA: #GitHub Action tj-actions/changed-files was compromised to leak secrets
1. search through your organization for tj-actions/changed-files
2. review GitHub Actions logs
3. rotate secrets, if they leaked in the logs
www.stepsecurity.io/blog/harden-...
Take our #OpenTelemetry #Contributor Survey and help us enhance the contributor experience. We appreciate your time and feedback!
All things considered, personally doing ok, and slowly getting better.
Starting to show up publicly again. Not sure I have the coordination to skateboard, volleyball has been my midlife skill pickup
Hey! Long time. How's life treating you?
Survey closing in 10 days. If you use OTel as a developer, tell us about your experience!
Sad news indeed. Brendan was a force in any room. A great colleague and an old friend. He will be missed.
That was an excellent write up, Adam, thank you for that.
Turtles all the way down...
strongly recommend reading this post if you give a shit about the internet
Quite the evolution. Feel like I need to go back and find my photos
Are you a developer using or getting started with @opentelemetry.io and want to share your pain points with us?
This is your time to talk: buff.ly/3DbzvDX
#opentelemetry
It's really quite powerful. It also makes me wonder what the end state for ottl will be.
My suspicion is that structured processing and streaming data are implicitly hard and query/processing languages have complexity that you can't actually remove without making it useless.
lazy web poll for #opentelemetry community. If you're using a tool and you see it uses jq (jqlang.github.io/jq/).
You would:
1. Do cool, powerful stuff.
2. Think: "This is easy".
3. Ignore it for built in "query" helpers.
4. Run away screaming.
Select all that apply.
You could argue that's the point of abstraction - I don't want to care (until it's not working).
Last point I'd disagree with.
The goal in o11y around unknown unknowns is having a bare minimum mechanism of *gaining* understanding.
The reality is folks aren't motivated to learn their full system until there's a problem.
Last week at #KubeCon, we announced #OpenTelemetry Community Awards winners! Thank you to all who submitted nominations. Two of our winners received their plaques in person at KubeCon.
Check out our blog post below to find out who won, and who was nominated! ⬇️
https://buff.ly/4eN5SpW
I started with advent of code, moved onto weaver and now do more aggressive things, like microcontroller, bevy and this thing GitHub.com/jsuereth/otlp-mmap
If you want a no risk starter project, we could use help on GitHub.com/open-telemetry/weaver
