Bird
0
0

A developer sends custom metrics to CloudWatch but no data appears in the console. Which is the most probable reason?

medium📝 Debug Q7 of 15
AWS - CloudWatch
A developer sends custom metrics to CloudWatch but no data appears in the console. Which is the most probable reason?
AThe custom metric namespace was not specified correctly
BThe EC2 instance does not have an IAM role attached
CCloudWatch does not support custom metrics
DThe AWS CLI version is outdated
Step-by-Step Solution
Solution:
  1. Step 1: Check metric namespace

    Custom metrics must be sent with a valid namespace; incorrect or missing namespaces cause metrics not to appear.
  2. Step 2: Evaluate other options

    IAM roles affect permissions but usually cause errors; CloudWatch supports custom metrics; CLI version issues typically cause errors, not silent failures.
  3. Final Answer:

    The custom metric namespace was not specified correctly -> Option A
  4. Quick Check:

    Correct namespace required for custom metrics [OK]
Quick Trick: Namespace must be correct for metrics to appear [OK]
Common Mistakes:
  • Ignoring namespace correctness
  • Assuming IAM role issues cause silent failures
  • Believing CloudWatch doesn't support custom metrics

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes