Service Mesh Observability

by wshobson46891e7e60daNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.

Instructions onlyDevOps & Cloud
AI-generated overview

Guide to service mesh observability covering tracing, metrics, logs, golden signals and SLOs for Istio and Linkerd.

What it does
This skill provides instructional guidance on implementing observability for service meshes such as Istio and Linkerd. It explains the three pillars of observability (metrics, traces, logs), the golden signals for mesh traffic, and best practices for sampling, trace context propagation, alerting and retention. It points to a reference file for full templates and worked examples.
When to use it
Use it when setting up distributed tracing or mesh metrics and dashboards, debugging latency or error issues in service communication, defining SLOs, visualizing service dependencies, or troubleshooting mesh connectivity.
Requirements
No scripts are included; it is instructions only. It references a companion file, references/details.md, for templates and worked examples. No specific tools, packages, credentials or network access are stated.

Service 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

SignalDescriptionAlert Threshold
LatencyRequest duration P50, P99P99 > 500ms
TrafficRequests per secondAnomaly detection
Errors5xx error rate> 1%
SaturationResource 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

Source and attribution

Source:wshobson/agentsinplugins/cloud-infrastructure/skills/service-mesh-observabilityat commit46891e7

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal