A game studio runs about 60 Linux dedicated game servers on Amazon EC2. The operations team wants memory and disk usage on each server in CloudWatch, at one-minute resolution.
The game engine is not instrumented for metrics, and the team does not want to change the game code to publish them. The team also wants the agent's settings to be kept in one place that every server reads, so that a change to the collected metrics reaches the whole fleet at once.
Which approach meets these requirements?
Choose one answer.
AA. Rely on the default EC2 metrics, which already include memory and disk usage for every instance at one-minute resolution, and create alarms on them.
BB. Add code to the game server that calls PutMetricData with memory and disk values every minute, give each host permission to publish, and deploy the change with the next game update.
CC. Install the CloudWatch agent on each server with a configuration that collects memory and disk metrics, and keep that configuration in one Parameter Store parameter that every server reads.
DD. Turn on VPC Flow Logs for the subnets where the game servers run, and create metric filters on the flow log records to count the bytes each server sends and receives.
The CloudWatch agent collects guest-level memory and disk usage that EC2 does not publish by default, and its configuration can live in Parameter Store so every server reads the same settings. Default metrics, code changes and flow logs each miss the memory and disk values or change the game.
Want more on CloudWatch agent and metric streams? The 5 full-length practice sets have 9 more CloudWatch agent and metric streams questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →