New to Claude Skills? Learn how to install them →

wshobson on GitHub

Service Mesh Observability

Free

Comprehensive observability patterns for service meshes.

by wshobson38.7k stars on wshobson/agents
1 views
Updated Jul 18, 2026
Get this skill

Free · Opens the source repo

What Service Mesh Observability does

Service Mesh Observability provides a complete guide to implementing observability patterns specifically tailored for service mesh technologies like Istio and Linkerd. This skill is designed to help developers and operations teams set up distributed tracing, monitor service metrics, and visualize service dependencies effectively. With a focus on debugging latency issues and defining service level objectives (SLOs), it equips users with the necessary tools and best practices to ensure robust service mesh performance.

The skill outlines the three core pillars of observability: metrics, traces, and logs. Each pillar plays a crucial role in understanding service behavior and performance. Metrics provide insights into request rates, error rates, and latency, while traces help in tracking the flow of requests through various services. Logs offer detailed information about access and error events, contributing to a comprehensive observability strategy. By understanding these components, teams can proactively address performance bottlenecks and improve overall system reliability.

Additionally, the skill introduces the concept of golden signals—key performance indicators that help teams monitor service health. These include latency, traffic, errors, and saturation, each with defined alert thresholds to facilitate timely responses to potential issues. The included best practices guide users on how to implement observability effectively, emphasizing the importance of appropriate sampling, alert setups, and cost management.

For those looking to deepen their understanding, the skill also provides a library of templates and detailed worked examples, making it easier to apply these concepts in real-world scenarios. Overall, Service Mesh Observability is an essential tool for anyone involved in managing service meshes, ensuring that they can maintain high levels of service performance and reliability.

When to use it

Use this skill when setting up observability for service meshes, particularly for distributed tracing, metrics, and visualizations.

When not to use it

This skill may not be suitable for users looking for observability solutions outside of service meshes or those needing real-time monitoring capabilities.

What you can build with it

Setting Up Distributed Tracing

Utilize the skill to implement distributed tracing across your services, allowing for better tracking of request flows and performance analysis.

Monitoring Service Metrics

Leverage the guidance provided to set up metrics and dashboards that visualize service performance, helping identify issues before they impact users.

Defining Service Level Objectives (SLOs)

Use the skill to establish SLOs for service communication, ensuring that your services meet performance expectations and maintain reliability.

How to install Service Mesh Observability

View source

1. Install with the skills CLI

npx skills add wshobson/agents/service-mesh-observability --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by wshobson

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

Frequently asked questions about Service Mesh Observability

Similar skills