Ready to go deeper?
| Course | Description | Status |
|---|---|---|
| Instrumentation Hub | Zero-code auto-instrumentation on Kubernetes | Future |
| Manual service instrumentation | OpenTelemetry SDK for non-K8s environments | Future |
| Knowledge Graph | Entity catalog, insights, RCA Workbench | Future |
| Application observability | Service Inventory, RED metrics, dependencies | Future |
Operational practices for Level 2
| Course | Description | Status |
|---|---|---|
| Service alerting | Error rate alerts, service investigation | Future |
| Service SLOs | Availability targets, burn rate alerts | Future |
| Service dashboards | Service health, dependency views | Future |
Documentation
Once you can identify which service is the problem, you’re ready for Level 3.
Script
If Level 2 is your focus, here are the paths forward.
Instrumentation Hub teaches you to discover services and enable zero-code instrumentation on Kubernetes using Beyla. If you’re not on Kubernetes or need more control, Manual Service Instrumentation covers setting up OpenTelemetry SDK to get basic service telemetry flowing.
Once you have service data, Knowledge Graph helps you understand your system topology and troubleshoot with the RCA Workbench. Application Observability gives you the Service Inventory, RED metrics, and dependency views.
On the operational side, we’re planning courses on Service Alerting, Service SLOs, and Service Dashboards. These will teach you how to operationalize all that service visibility.
Check the documentation links on this slide if you want to start exploring these features now. The docs are comprehensive.
Once you can confidently identify which service is causing a problem, you’re ready for Level 3. That’s where we dig into why specific requests are slow.