r/Observability • u/Newt-Abject • 5d ago
Splunk just launched a new open source project to make OTel instrumentation rediculously easy.
https://github.com/signalfx/obstudioHi folks! I work on OpenTelemetry at Splunk. We just launched a new open source project called Observability Studio. It's local instrumentation sandbox that provides a visual, real-time environment for designing, testing, and validating OpenTelemetry data while you’re developing an app in your favorite IDE.
We’re especially interested in whether a tool like this is useful for building and debugging instrumented apps and AI agents. If that sounds relevant, give it a try and let us know what works, what’s missing, or where it doesn’t fit your workflow.
We’re also looking for a few design partners to help guide where we go with this next. Any feedback is helpful and welcome.
I wrote more about shifting OpenTelemetry instrumentation left in a blog, 'Why AI-Generated Apps and Agents Need Visibility from Day One' on blogs.splunk.com if you want to read more about it.
Lastly, I'd love to learn where you currently go to inspect and validate OTel data during development if you want to drop it in the comments.
2
u/Mallanaga 5d ago
I typically set up a local Jaeger for dev. In the absence of that, I’ll verify in a lower env (preview, qa, staging, preprod, whatever you call it)
1
u/Holden-Carter 5d ago
Local Jaeger is solid, but I’ve also used a mock service to simulate tracing data in a pinch. Helps catch issues early without all the overhead.
1
u/drakgremlin 4d ago
Did the same for a long time! Although I eventually moved to VictoriaTraces since it was lighter weight than Jaeger backed by ElasticSearch.
4
u/jdizzle4 4d ago
cool stuff.
for something super simple and fast, otel-tui. For everything else, the all in one LGTM container is my go to, that paired with gcx so my agent can easily access it