Instrumentation choice is slowing adoption before a workload ever sends useful telemetry.
A broad recommendation protects more workload types, while a narrow first release protects clarity and trust.
Who you’d be doing this for
“Every service owner asks which path to use, and I’m still answering from a spreadsheet.”
Marta Dubois · Platform Engineer
Sets instrumentation standards for application teams running Kubernetes workloads.
What is at stake
Users abandon setup after comparing SDK, Beyla, and Collector paths with no trusted recommendation. You must weigh broad workload coverage against a first version that users and coding agents can verify.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- broad workload coverage vs first-version clarity
- agent-ready guidance vs human review
- recommendation precision vs setup completion
- automatic instrumentation vs path neutrality
Why Grafana
Grafana Cloud already supports SDK onboarding, Beyla, and OpenTelemetry Collector deployment, but customers need one coherent way to choose among them.
Written with these in mind
Not your kind of problem? 24 more at Grafana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.