S
service-mesh-observability
About service-mesh-observability
A practical guide to observability for Istio, Linkerd, and other service mesh deployments. It helps teams configure metrics, traces, logs, alerts, and dependency views, with guidance on SLOs and troubleshooting.
Key features
- 01Metrics, traces, and logs guidance
- 02Golden signals and alert thresholds
- 03Sampling and trace context practices
- 04Metric and trace correlation
- 05Observability templates and examples
Use cases
- 01Set up distributed tracing across services
- 02Build service mesh dashboards and alerts
- 03Investigate latency and error problems
- 04Define communication SLOs and dependencies
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/service-mesh-observabilityin Claude Code to confirm it loaded.
Bundled filesreferences/details.md
Details
From the project READMEService Mesh Observability
Complete guide to observability patterns for Istio, Linkerd, and service mesh deployments.
When to Use This Skill
- Setting up distributed tracing across services
- Implementing service mesh metrics and dashboards
- Debugging latency and error issues
- Defining SLOs for service communication
- Visualizing service dependencies
- Troubleshooting mesh connectivity
Core Concepts
1. Three Pillars of Observability
┌─────────────────────────────────────────────────────┐
│ Observability │
├─────────────────┬─────────────────┬─────────────────┤
│ Metrics │ Traces │ Logs │
│ │ │ │
│ • Request rate │ • Span context │ • Access logs │
│ • Error rate │ • Latency │ • Error details │
│ • Latency P50 │ • Dependencies │ • Debug info │
│ • Saturation │ • Bottlenecks │ • Audit trail │
└─────────────────┴─────────────────┴─────────────────┘
2. Golden Signals for Mesh
| Signal | Description | Alert Threshold |
|---|---|---|
| Latency | Request duration P50, P99 | P99 > 500ms |
| Traffic | Requests per second | Anomaly detection |
| Errors | 5xx error rate | > 1% |
| Saturation | Resource utilization | > 80% |
Templates and detailed worked examples
Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.
Best Practices
Do's
- Sample appropriately - 100% in dev, 1-10% in prod
- Use trace context - Propagate headers consistently
- Set up alerts - For golden signals
- Correlate metrics/traces - Use exemplars
- Retain strategically - Hot/cold storage tiers
Don'ts
- Don't over-sample - Storage costs add up
- Don't ignore cardinality - Limit label values
- Don't skip dashboards - Visualize dependencies
- Don't forget costs - Monitor observability costs
Comments
Markdown supported