Domain
Observability & Monitoring
Skill Profile
Jaeger / Grafana Tempo
Distributed tracing, trace analysis, service dependencies, sampling
Observability & Monitoring
Distributed Tracing
Roles
1
where this skill appears
Levels
5
structured growth path
Mandatory requirements
3
the other 2 optional
Group
Distributed Tracing
Last updated
3/17/2026
How to Use
Choose your current level and compare expectations. The items below show what to cover to advance to the next level.
What is Expected at Each Level
The table shows how skill depth grows from Junior to Principal. Click a row to see details.
| Role | Required | Description |
|---|---|---|
| Site Reliability Engineer (SRE) | Understands the fundamentals of Jaeger / Grafana Tempo. Applies basic practices in daily work. Follows recommendations from the team and documentation. |
| Role | Required | Description |
|---|---|---|
| Site Reliability Engineer (SRE) | Configures Jaeger / Grafana Tempo for services. Creates dashboards and alerts. Participates in on-call rotation. Analyzes incidents. |
| Role | Required | Description |
|---|---|---|
| Site Reliability Engineer (SRE) | Required | Designs observability strategy with Jaeger / Grafana Tempo. Implements distributed tracing. Defines SLI/SLO. Conducts post-mortems. |
| Role | Required | Description |
|---|---|---|
| Site Reliability Engineer (SRE) | Required | Defines tracing standards: mandatory spans, sampling rates, retention policies. Implements Tempo/Jaeger for distributed tracing. Uses traces for dependency mapping and bottleneck analysis. |
| Role | Required | Description |
|---|---|---|
| Site Reliability Engineer (SRE) | Required | Designs distributed tracing platform: Tempo vs Jaeger vs managed, sampling strategy (head vs tail-based), traces-to-metrics conversion. Defines tracing governance. |
Loading comments...
Sign In to join the discussion