Compétences observability-monitoring-monitor-setup
📩

observability-monitoring-monitor-setup

Sûr

Set up comprehensive monitoring and observability

Implementing monitoring from scratch is complex and error-prone. This skill provides proven patterns for metrics, tracing, and logging that reduce MTTR and give full system visibility.

Prend en charge: Claude Codex Code(CC)
đŸ„‰ 74 Bronze
1

Télécharger le ZIP du skill

2

Importer dans Claude

Allez dans ParamĂštres → CapacitĂ©s → Skills → Importer un skill

3

Activez et commencez Ă  utiliser

Tester

Utilisation de "observability-monitoring-monitor-setup". Set up Prometheus scraping for a Kubernetes cluster with automatic pod discovery

RĂ©sultat attendu:

  • Prometheus configuration with kubernetes_sd_configs for auto-discovery
  • Pod annotations required for scrape targeting
  • Relabel rules to filter and tag discovered targets
  • Verification steps to confirm scraping is working

Utilisation de "observability-monitoring-monitor-setup". Create an alert for memory usage exceeding 90%

RĂ©sultat attendu:

  • PromQL expression using container_memory_working_set_bytes
  • Alert rule with appropriate thresholds and duration
  • Runbook steps for investigating memory pressure
  • Grafana panel query to visualize memory trends

Audit de sécurité

Sûr
v1 ‱ 2/24/2026

This skill contains documentation and code samples for monitoring setup. All static analysis findings are false positives - backticks are markdown code block delimiters, not shell execution. URLs are internal service endpoints. Environment variable usage follows standard configuration patterns. No malicious patterns detected.

2
Fichiers analysés
557
Lignes analysées
0
résultats
1
Total des audits
Aucun problÚme de sécurité trouvé
Audité par: claude

Score de qualité

38
Architecture
100
Maintenabilité
87
Contenu
50
Communauté
100
Sécurité
91
Conformité aux spécifications

Ce que vous pouvez construire

Greenfield Service Monitoring

Set up complete observability stack for a new microservice from day one with metrics, tracing, and logging.

Production Incident Response

Create actionable dashboards and alerts to reduce MTTR and enable proactive issue detection.

SLO Definition and Tracking

Define service level objectives with error budgets and implement burn rate monitoring for reliability engineering.

Essayez ces prompts

Basic Metrics Setup 
Help me add Prometheus metrics to my Node.js API. I need request count, error rate, and latency tracking. Show me the prom-client setup and how to expose a /metrics endpoint.
Grafana Dashboard Creation 
Create a Grafana dashboard JSON for my payment service showing the four golden signals. Include panels for request rate, error rate, p95/p99 latency, and saturation metrics.
Alert Configuration 
I need alerting rules for high error rate (>5% for 5 minutes) and slow response time (p95 >1s for 10 minutes). Configure Alertmanager to route critical alerts to PagerDuty and warnings to Slack.
SLO Implementation 
Define SLOs for my API with 99.9% availability target over 30 days. Show me how to calculate error budget, set up multi-window burn rate alerts, and create Grafana panels for SLO tracking.

Bonnes pratiques

  • Use histogram buckets aligned with your SLO targets for accurate percentile calculation
  • Add consistent labels (service, environment, version) to all metrics for effective filtering
  • Test alerts against historical data to minimize false positives before enabling notifications

Éviter

  • Monitoring everything without clear ownership leads to alert fatigue and ignored pages
  • Using average latency instead of percentiles hides tail latency problems affecting users
  • Setting up dashboards before defining what questions they need to answer wastes effort

Foire aux questions

How do I choose the right scrape interval for my metrics?
Start with 15s for most services. Use 5s for latency-sensitive systems or when debugging. Avoid intervals below 5s as they increase Prometheus load without proportional benefit.
Should I trace every request or sample?
Sample in production. Use head-based sampling (e.g., 10% of requests) for high-traffic services. Trace 100% in staging. Always trace errors regardless of sampling rate.
What is the difference between RED and USE monitoring?
RED (Rate, Errors, Duration) is for user-facing services. USE (Utilization, Saturation, Errors) is for infrastructure resources. Use RED for application monitoring, USE for nodes and databases.
How do I set meaningful SLO targets?
Base targets on user expectations and business requirements, not current performance. Start conservative (99%) and tighten as reliability improves. Measure over 28-30 day windows.
Do I need all three pillars (metrics, logs, traces) from day one?
Start with metrics - they are cheapest and answer 'what is broken'. Add logging for 'why it broke'. Add tracing for distributed systems when debugging cross-service issues becomes difficult.
How long should I retain monitoring data?
Keep high-resolution metrics (raw samples) for 15-30 days for debugging. Use downsampling or recording rules for long-term trends. Store logs based on compliance requirements, typically 90 days minimum.

Détails du développeur

Auteur

sickn33

Licence

MIT

DĂ©pĂŽt

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/observability-monitoring-monitor-setup

RĂ©f

main

Structure de fichiers

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md