Why monitoring matters in AWS - Performance Analysis

Time Complexity: Why monitoring matters

O(n)

Understanding Time Complexity

Monitoring in AWS helps us keep track of how systems perform over time.

We want to understand how the cost of monitoring changes as the amount of data grows.

Scenario Under Consideration

Analyze the time complexity of the following AWS CloudWatch metric retrieval code.

const AWS = require('aws-sdk');
const cloudwatch = new AWS.CloudWatch();

async function getMetrics(metricNames) {
  const results = [];
  for (const name of metricNames) {
    const data = await cloudwatch.getMetricData({
      MetricDataQueries: [{ Id: 'm1', MetricStat: { Metric: { MetricName: name, Namespace: 'AWS/EC2' }, Period: 60, Stat: 'Average' }, ReturnData: true }]
    }).promise();
    results.push(data);
  }
  return results;
}

This code fetches metric data for each metric name from AWS CloudWatch one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop over each metric name to fetch data.
• How many times: Once per metric name in the input list.

How Execution Grows With Input

As the number of metric names increases, the number of fetch calls grows the same way.

Input Size (n)	Approx. Operations
10	10 metric fetch calls
100	100 metric fetch calls
1000	1000 metric fetch calls

Pattern observation: The work grows directly with the number of metrics to fetch.

Final Time Complexity

Time Complexity: O(n)

This means the time to get all metrics grows in a straight line as you add more metrics.

Common Mistake

[X] Wrong: "Fetching multiple metrics at once is always faster regardless of how many there are."

[OK] Correct: Sometimes fetching many metrics individually can slow things down because each call waits for the last one to finish.

Interview Connect

Understanding how monitoring scales helps you design systems that stay reliable as they grow.

Self-Check

"What if we fetched all metrics in a single batch call instead of one by one? How would the time complexity change?"

Practice

1. Why is monitoring important in AWS environments?

easy

A. It helps detect issues early to keep systems running smoothly.

B. It automatically fixes all system errors without human help.

C. It increases the cost of running AWS services.

D. It disables alarms to reduce notifications.

Solution

1. Step 1: Understand monitoring purpose

   Monitoring tracks system health and performance in real time.

2. Step 2: Identify the benefit of early detection

   Early detection helps fix problems before they affect users.

3. Final Answer:

   It helps detect issues early to keep systems running smoothly. -> Option A

4. Quick Check:

   Monitoring = Early issue detection [OK]

Hint: Monitoring = early alerts to avoid bigger problems [OK]

Common Mistakes:

• Thinking monitoring fixes issues automatically
• Believing monitoring increases costs unnecessarily
• Assuming monitoring disables alarms

2. Which AWS service is primarily used for monitoring and setting alarms?

easy

A. Amazon CloudWatch

B. Amazon EC2

C. AWS S3

D. AWS Lambda

Solution

1. Step 1: Identify AWS monitoring services

   AWS CloudWatch collects metrics and logs for monitoring.

2. Step 2: Match service to alarms and monitoring

   CloudWatch allows setting alarms to notify on issues.

3. Final Answer:

   Amazon CloudWatch -> Option A

4. Quick Check:

   Monitoring + alarms = CloudWatch [OK]

Hint: CloudWatch = AWS monitoring and alarms tool [OK]

Common Mistakes:

• Confusing Lambda with monitoring service
• Thinking S3 stores monitoring data directly
• Assuming EC2 handles alarms

3. What will happen if you create a CloudWatch alarm for CPU usage > 80% and the CPU usage reaches 85%?

medium

A. The CPU usage will automatically reduce.

B. The alarm will ignore the CPU usage.

C. The alarm will trigger and notify you.

D. The alarm will delete the instance.

Solution

1. Step 1: Understand CloudWatch alarm behavior

   Alarms trigger when the monitored metric crosses the threshold.

2. Step 2: Apply to CPU usage scenario

   CPU usage > 80% triggers the alarm at 85% usage.

3. Final Answer:

   The alarm will trigger and notify you. -> Option C

4. Quick Check:

   CPU > threshold = alarm triggers [OK]

Hint: Alarm triggers when metric exceeds threshold [OK]

Common Mistakes:

• Thinking alarms fix issues automatically
• Believing alarms ignore threshold breaches
• Assuming alarms delete resources

4. You set a CloudWatch alarm but never receive notifications when thresholds are crossed. What is a likely cause?

medium

A. The CPU usage never exceeded the threshold.

B. The alarm is not linked to any notification action.

C. CloudWatch does not support alarms.

D. The AWS account is inactive.

Solution

1. Step 1: Check alarm configuration

   Alarms must have notification actions (like SNS) to send alerts.

2. Step 2: Identify missing notification setup

   If no notification is linked, no alerts are sent despite threshold breaches.

3. Final Answer:

   The alarm is not linked to any notification action. -> Option B

4. Quick Check:

   Missing notification = no alerts [OK]

Hint: Link alarms to notifications to get alerts [OK]

Common Mistakes:

• Assuming alarms send notifications automatically
• Ignoring notification setup in alarm
• Thinking CloudWatch lacks alarm support

5. You want to keep your AWS app reliable by monitoring multiple metrics and sending alerts only when several conditions happen together. Which approach should you use?

hard

A. Create multiple independent CloudWatch alarms without combining them.

B. Disable alarms to reduce noise.

C. Rely on manual checks instead of alarms.

D. Use CloudWatch composite alarms to combine multiple alarms into one alert.

Solution

1. Step 1: Understand composite alarms

   Composite alarms combine multiple alarms using logical conditions.

2. Step 2: Apply composite alarms for multi-condition alerts

   This lets you alert only when all or some conditions happen together.

3. Final Answer:

   Use CloudWatch composite alarms to combine multiple alarms into one alert. -> Option D

4. Quick Check:

   Multi-condition alert = composite alarms [OK]

Hint: Use composite alarms for combined conditions [OK]

Common Mistakes:

• Creating separate alarms without combination
• Ignoring composite alarms feature
• Disabling alarms to avoid alerts