Q: A developer complains that their new logs aren't showing up in CloudWatch. They verified the IAM Role has permission to write logs. What else could be wrong?
If the IAM permissions are correct (i.e., logs:CreateLogStream, logs:PutLogEvents), the issue is often configuration:
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During a high-traffic production event, our observability stack proved essential in isolating this latency surge. The interviewer is testing: CloudWatch agent configuration, log stream structure.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
If the IAM permissions are correct (i.e., logs:CreateLogStream, logs:PutLogEvents), the issue is often configuration:
- Agent Configuration: If using the unified CloudWatch agent on EC2, the
/opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.jsonmust be configured to list the exact absolute path to the log file. - Service restart: The agent must be restarted to pick up config file changes.
- Log Group constraints: If the application creates log streams dynamically, check if the AWS account has hit a rate limit, or if the KMS key encrypting the log group lacks permissions for the compute service to use it.
Remediation & Permanent Safeguards
- Time synchronization: If the EC2 instance NTP clock is drastically delayed or ahead, CloudWatch will reject the log events stating the timestamps are invalid.
- Agent Configuration: If using the unified CloudWatch agent on EC2, the /opt/aws/amazon-cloudwatch...
- Service restart: The agent must be restarted to pick up config file changes.
- Log Group constraints: If the application creates log streams dynamically, check if the AWS accou...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability developer complains High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability developer complains Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability developer complains Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability developer complains Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.