Which monitoring capability is essential for identifying performance bottlenecks in real-time in an ECS environment?

Question

Options

• AAesthetic monitoring of the ECS console
• BApplication-level performance metrics
• CDaily manual log reviews
• DNetwork latency measurements

• A
  3% (1)
• B
  90% (36)
• C
  5% (2)
• D
  3% (1)

Explanation

Application-level performance metrics (B) are essential because they provide granular, real-time insight into how containers and services are actually behaving - CPU usage, memory consumption, request latency, error rates, and throughput - which are the signals needed to pinpoint where a bottleneck is occurring inside ECS tasks or services.

A is wrong because "aesthetic monitoring" of the ECS console is not a real monitoring capability; passively glancing at a UI without actionable metrics does not identify bottlenecks.

C is wrong because daily manual log reviews are reactive and far too slow for real-time bottleneck detection - by the time you review them, the performance issue has likely already impacted users.

D is wrong because network latency measurements are one narrow metric that only covers connectivity between components, not the broader application-level performance (CPU spikes, memory leaks, slow DB queries) that typically cause bottlenecks.

Memory tip: Think of the word application as the key - bottlenecks live in the app, so you need app-level metrics. The other options are either too surface-level (console aesthetics), too slow (daily logs), or too narrow (just network).

No community discussion yet for this question.