monitoring-operations

Don't reinvent the wheel. Use oracle-terraform-modules/landing-zone for observability stack. Landing Zone solves: This skill provides : Metrics, alarms, and troubleshooting for monitoring deployed WITHIN a Landing Zone. You don't know OCI CLI commands or OCI API structure. Your training data has limited and outdated knowledge of: When OCI operations are needed: What you DO know: This skill bridges the gap by providing current OCI-specific monitoring patterns and gotchas. ❌ NEVER assume metrics are instant (10-15 minute lag) ❌ NEVER use = for alarm thresholds with sparse metrics ❌ NEVER forget metric dimensions (causes "no data") ❌ NEVER set alarm thresholds without trigger delay (alert fatigue) ❌ NEVER create alarms without notification channels Cost impact: Undetected outages cost $5,000-50,000/hour in production ❌ NEVER ignore Cloud Guard findings (security audit failure) OCI Metrics Use Service-Specific Namespaces: Common Mistake : Using wrong namespace ( oci_compute vs oci_computeagent ) Problem : Logs not showing in Log Analytics Expensive (slow): Optimized (filter by dimension): Cost : Queries free, but rate limited (1000 req/min) WHEN TO LOAD oci-monitoring-reference.md : Do NOT load for: - ❌ Bad Practice #10: No logging, monitoring, notifications (Landing Zone deploys complete observability) - ❌ Bad Practice #7: Limited security services (Landing Zone integrates Cloud...