Implement application observability
Implement the three pillars of observability (logs, metrics, traces) with OpenTelemetry, Prometheus and Grafana dashboards.
Paste in your AI
Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.
Tu es un expert SRE (Site Reliability Engineering) spécialisé dans l'observabilité des systèmes distribués. Je dois mettre en place les trois piliers de l'observabilité pour mon application. **Application à instrumenter :** - Type : [EX: API Node.js, microservices Python, application Go] - Infrastructure : [EX: Kubernetes, Docker Compose, VPS simple] - Volume de trafic : [EX: 10k requêtes/minute] - Stack actuelle : [EX: aucun monitoring, Sentry uniquement, logs basiques] **Outils disponibles ou souhaités :** - Logs : [EX: Loki + Grafana, ELK Stack, Datadog] - Métriques : [EX: Prometheus + Grafana, CloudWatch, Datadog] - Traces : [EX: Jaeger, Zipkin, Tempo, Datadog APM] Mets en place les trois piliers de l'observabilité : 1. **Logging structuré** : implémente le logging JSON avec des champs standards (timestamp, level, service, trace_id, user_id, duration). Définis les niveaux de log et quand utiliser chacun. Évite les logs inutiles qui noient les logs importants. 2. **Métriques Prometheus** : instrumente les métriques métier clés (taux de succès des commandes, revenus par heure) et techniques (latence P95/P99, taux d'erreur, utilisation des ressources). Fournis le code d'instrumentation. 3. **Tracing distribué avec OpenTelemetry** : configure le SDK OpenTelemetry, instrumente les routes HTTP et les appels de base de données, propage le trace context entre services. 4. **Dashboards Grafana** : propose la définition JSON de 3 dashboards : vue d'ensemble de santé, latence et erreurs, et métriques métier. 5. **Alertes** : définis des règles d'alerte pertinentes avec des seuils basés sur les SLOs (Service Level Objectives) et le budget d'erreur.
Why this prompt works
<p>This prompt structures observability according to the three pillars recognized by the industry (logs, metrics, traces), which ensures complete system visibility: logs for error context, metrics for trends and alerts, and traces for understanding interactions between services.</p><p>The distinction between technical metrics and business metrics is fundamental for product teams: knowing that P99 latency is 500ms is useful for engineering, but knowing that order success rate has dropped by 5% is critical information for the business. Both types of metrics must coexist.</p><p>Adopting OpenTelemetry for tracing is a wise strategic choice because it's the open-source standard that avoids vendor lock-in: the same instrumentation code can send traces to Jaeger, Tempo or Datadog according to needs, without modifying the application code.</p>
Use Cases
Expected Output
Complete configuration of the three pillars with instrumentation code, Grafana dashboards and alert rules based on SLOs.
Learn more
Check the full skill on Prompt Guide to master this technique from A to Z.
View on Prompt GuideGlossary Terms
Similar Prompts
Learn the basics of Git for beginners
Learn Git from scratch with illustrated explanations, concrete examples, a practical workflow and a cheatsheet of essential commands.
Define a Git strategy for a team
Define a comprehensive Git strategy adapted to your team: branching model, conventions, code review and release management.
Write integration tests for an API
Create comprehensive API integration tests with database setup, authentication, CRUD and end-to-end scenarios.
Create an optimized Dockerfile for production
Create an optimized multi-stage Dockerfile for production with maximum security, lightweight image and best practices.