Claude Cursor Skill

service-mesh-observability

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.

LLM Mart · 0 points · 18 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_cloud-infrastructure_skills_service-mesh-observability-554237f.zip · 3 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/cloud-infrastructure/skills/service-mesh-observability
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

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
Files (agents)
  • references
    • details.md 7.5 KB
      Loading…
  • SKILL.md 2.8 KB
    ---
    name: service-mesh-observability
    description: 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.
    ---
    
    # 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
    
    | 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 (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.