Habilidades service-mesh-observability
📦

service-mesh-observability

Seguro

Implement Service Mesh Observability

Também disponível em: wshobson

Set up comprehensive monitoring, tracing, and alerting for your service mesh deployments. Get ready-to-use configurations for Istio, Linkerd, Prometheus, Grafana, and Jaeger.

Suporta: Claude Codex Code(CC)
🥉 75 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "service-mesh-observability". Generate Prometheus config for Istio metrics

Resultado esperado:

YAML ServiceMonitor with scrape configs targeting istiod endpoints, 15 second intervals, and relabel rules for mesh discovery.

A utilizar "service-mesh-observability". Create alert for high latency

Resultado esperado:

PrometheusRule with histogram_quantile expression for P99 latency threshold, 5 minute evaluation window, and warning severity annotation.

Auditoria de Segurança

Seguro
v1 • 2/25/2026

This skill is a documentation-only guide for service mesh observability. Static analysis flagged 55 patterns, but all are false positives: backtick commands are markdown code blocks (not execution), hardcoded URLs/IPs are configuration examples, and crypto warnings are triggered by YAML config snippets. No actual code execution, network calls, or filesystem operations occur.

1
Arquivos analisados
398
Linhas analisadas
0
achados
1
Total de auditorias
Nenhum problema de segurança encontrado
Auditado por: claude

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
100
Segurança
100
Conformidade com especificações

O Que Você Pode Construir

Platform Engineer Setting Up Mesh Monitoring

Deploy complete observability stack for new Istio installation with Prometheus, Grafana, and Jaeger integration.

SRE Debugging Production Latency Issues

Query distributed traces to identify bottlenecks across microservices and set up P99 latency alerts.

DevOps Team Implementing SLOs

Define and monitor service level objectives for mesh traffic with automated alerting on error rate thresholds.

Tente Estes Prompts

Basic Mesh Metrics Setup 
Generate a Prometheus ServiceMonitor configuration for scraping Istio mesh metrics with 15 second intervals.
Distributed Tracing Configuration 
Create a Jaeger deployment manifest for Istio tracing with 100 percent sampling for development environments.
Grafana Dashboard Creation 
Build a Grafana dashboard JSON with panels for request rate, error rate, P99 latency, and service topology for Istio.
Production Alerting Rules 
Write PrometheusRule alerts for high error rate above 5 percent and P99 latency over 1 second with appropriate severity labels.

Melhores Práticas

  • Sample traces at 100 percent in development but reduce to 1-10 percent in production to control storage costs
  • Configure alerting on golden signals: latency, traffic, errors, and saturation with appropriate thresholds
  • Use trace context propagation consistently across all services for complete request visibility

Evitar

  • Over-sampling traces in production leading to excessive storage costs and performance overhead
  • Ignoring metric cardinality limits causing Prometheus memory issues and slow queries
  • Deploying observability tools without dashboards or alerts that provide actionable insights

Perguntas Frequentes

What service meshes does this skill support?
Primary support for Istio and Linkerd with configurations for Prometheus, Grafana, Jaeger, Kiali, and OpenTelemetry integration.
Does this skill deploy resources to my cluster?
No. This skill generates configuration templates and manifests that you review and apply manually with kubectl apply.
What sampling rate should I use for tracing?
Use 100 percent in development for complete visibility. In production, start with 10 percent and adjust based on traffic volume and storage budget.
Can I use this with managed service meshes?
Yes. Configurations work with managed Istio (GKE, AKS, EKS) and Linkerd, though some installation steps may differ from self-managed deployments.
How do I correlate metrics with traces?
Use Prometheus exemplars to link metric datapoints to trace spans. Configure your tracing backend to expose trace IDs in metric metadata.
What are the golden signals for service mesh?
Latency (request duration), Traffic (requests per second), Errors (5xx rate), and Saturation (resource utilization). Alert on anomalies in these metrics.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/service-mesh-observability

Referência

main

Estrutura de arquivos

📄 SKILL.md