Use when setting up metrics, alarms, or troubleshooting missing data in OCI Monitoring. Covers metric namespace confusion, alarm threshold gotchas, log collection setup, and common monitoring gaps.

OCI Monitoring and Observability Expert Knowledge 🏗️ Use OCI Landing Zone Terraform Modules Don't reinvent the wheel. Use [oracle terraform modules/landing zone](https://github.com/oracle terraform modules/terraform oci landing zones) for observability stack. Landing Zone solves: ❌ Bad Practice 10: No logging, monitoring, notifications (Landing Zone deploys complete observability) ❌ Bad Practice 7: Limited security services (Landing Zone integrates Cloud Guard, VSS, OSMS) This skill provides : Metrics, alarms, and troubleshooting for monitoring deployed WITHIN a Landing Zone. ⚠️ OCI CLI/API Knowledge Gap You don't know OCI CLI commands or OCI API structure. Your training data has limited and outdated knowledge of: OCI CLI syntax and parameters (updates monthly) OCI API endpoints and request/response formats Monitoring service CLI operations ( oci monitoring alarm , oci monitoring metric ) Metric namespaces and MQL (Monitoring Query Language) Latest Logging and Service Connector features When OCI operations are needed: 1. Use exact CLI commands from this skill's references 2. Do NOT guess metric namespace names 3. Do NOT assume AWS CloudWatch patterns work in OCI 4. Load reference files for detailed MQL documentation What you DO know: General observability concepts Alerting and threshold design principles Log aggregation patterns This skill bridges the gap by providing current OCI specific monitoring patterns and gotchas. NEVER Do This ❌ NEVER assume metrics are instant (10 15 minute lag) Metrics published every 1 5 minutes Processing delay: 5 10 minutes Total lag : 10 15 minutes from event to visible metric Don't debug "missing metrics" within first 15 minutes of resource creation ❌ 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) Cloud Guard detects misconfigurations BEFORE they become incidents Integrate Cloud Guard → Notifications → Email/Slack/PagerDuty Cost impact: $100,000+ per security breach vs $0 for proactive remediation Metric Namespace Gotchas OCI Metrics Use Service Specific Namespaces: Service Namespace Example Metric Compute oci computeagent CPUUtilization , MemoryUtilization Autonomous DB oci autonomous database CpuUtilization , StorageUtilization Load Balancer oci lbaas HttpRequests , UnHealthyBackendServers Object Storage oci objectstorage ObjectCount , BytesUploaded Common Mistake : Using wrong namespace ( oci compute vs oci computeagent ) Alarm Missing Data Handling Setting Behavior Use When treatMissingDataAsBreaching Alarm fires if no data Critical services (outage = breach) treatMissingDataAsNotBreaching Alarm silent if no data Optional monitoring {dataMissing=zero} Treat missing as 0 Counters (requests/sec) Log Collection Common Gaps Problem : Logs not showing in Log Analytics Metric Query Optimization Expensive (slow): Optimized (filter by dimension): Cost : Queries free, but rate limited (1000 req/min) Progressive Loading References OCI Monitoring Reference (Official Oracle Documentation) WHEN TO LOAD [ oci monitoring reference.md ](references/oci monitoring reference.md): Need comprehensive list of all OCI service metrics Understanding MQL (Monitoring Query Language) in depth Implementing complex alarm conditions and composites Need official Oracle guidance on Logging and Service Connector Setting up Log Analytics and APM integration Do NOT load for: Quick alarm setup (examples in this skill) Common metric patterns (tables above) Troubleshooting decision trees (covered above) When to Use This Skill Alarms: threshold configuration, missing data handling, trigger delay Troubleshooting: metrics not showing, alarms not firing, namespace errors Log collection: Service Connector, IAM policies, missing logs Performance: query optimization, dimension filtering

monitoring-operations