WAT?!?!
# general
m
WAT?!?!
👀 1
g
ha! this is exactly what @shaharglazner said in the interview 🙂 it isn't as bad as it sounds, since they all integrate with OpenTel, but yikes. We are overdue a consolidation. But before that, we are overdue a giant PDF that maps the space into tidy boxes 🙂
👋 1
I just tried Nobl9 yesterday, for SLOs. It is pretty great, but "do I really want another tool" definitely passed through my mind.
s
Yea we literally use this in our deck 😂
j
We were using 2 and wanted to replace them with less expensive options - now we have 4 🤷
s
The consolidation in this space is obvious, but it creates new problems such as vendor locking and the vendors make you pay so much because they know you can’t leave
m
How broadly defined is "observability tool" in this context? Like if someone says "we use this open source agent that integrates with 25 different backends, and we use one of those backends" does that count as two tools?
Versus "we use Splunk and ELK and Honeycomb and New Relic and Datadog and etc...."
k
If it's from a different vendor/project it's usually considered a separate tool. We've got a half dozen different tools for various usage, some connected to each other and others not
s
Super interesting, what’s the company size?
k
About 3000 developers, and very large telemetry volume
s
Oh this is pretty big. How would you describe the main pain points about this mega o11y architecture?
k
Storage scale, knowing what’s important and what isn’t, introducing change slowly, etc
g
"mega o11y architecture"! I love this 🙂
❤️ 3
r
I’m surprised Grafana considers itself separate from Grafana Loki and Grafana Tempo. I can’t imagine using grafana loki without grafana, to me it’s just a plugin that has external deps
g
Coincidentally, I just received a swag package from Nobl9. Including their card game “Paged at 3am”. Their instructions are funny:
😂 3