Observability Testing Patterns

<default_to_action> When testing observability infrastructure, dashboards, or monitoring:

1. VALIDATE data accuracy (source data matches what the dashboard displays)
2. TEST alert rules fire correctly at defined thresholds
3. VERIFY log aggregation completeness (no missing logs across services)
4. TRACE distributed requests end-to-end through APM
5. MEASURE dashboard performance (render time, query latency)
6. CONFIRM SLA/SLO compliance through synthetic monitoring
7. TEST metric pipeline integrity from collection to display

Quick Pattern Selection:

• Dashboard shows wrong numbers -> Data accuracy validation
• Alerts not firing -> Alert rule threshold testing
• Missing logs in Kibana -> Log aggregation completeness
• Slow dashboard -> Dashboard performance testing
• Broken traces -> APM trace validation
• SLA disputes -> SLO compliance validation