Two paths to Level 2
| Path | Best for | How it works |
|---|
| Instrumentation Hub (public preview) | Kubernetes environments | Zero-code instrumentation via Grafana Beyla |
| OpenTelemetry SDK | Non-K8s or custom needs | Auto-instrumentation libraries added to your app |
What is Beyla? A lightweight agent that observes your applications at the operating system level, capturing traces without any code changes. It outputs standard OpenTelemetry data.
Problems solved
| Problem | Solution |
|---|
| Instrumenting services takes months of dev work | Instrumentation Hub: minutes, no code changes |
| Don’t know which services lack instrumentation | Both paths show instrumentation gaps. |
| Vendor lock-in with proprietary agents | OpenTelemetry is industry standard. |
| Can’t instrument services you don’t control | Beyla captures traces without app changes. |
The tradeoff
| Instrumentation Hub | OpenTelemetry SDK |
|---|
| No code changes | Requires SDK addition |
| Kubernetes only | Works anywhere |
| Minutes to first traces | Deployment cycle required |
Both paths lead to the same destination
Traces flowing → RED metrics → Service visibility → Level 2 achieved