Configuring the Amazon CloudWatch Agent for Application-Specific Metrics

Fetch Application-Specific Metrics with Amazon CloudWatch Agent

Question

An IT firm is using the Amazon CloudWatch agent to collect system-level metrics from on-premises Linux Servers.

A new application is deployed on these servers.

The operations team is looking for specific metrics for this application in addition to system metrics. What configuration in the Amazon CloudWatch agent can be done to fetch application specific metrics?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer: B.

Amazon CloudWatch Agent can be set up to use multiple configuration files.

These files can fetch different metrics like system level or application specific metrics using multiple configuration files.

Multiple Configuration files can be created with different names & added to configuration files using the append-config command.

Options A & D are incorrect as to append additional config files, it needs to use append-config & not aggregate-config.

Option C is incorrect as if append-config is used with two Configuration files with the same file name, it will overwrite the first file.

In the above case, the client is looking for both metrics system level & application level.

For more information on using Multiple CloudWatch agent configuration files, refer to the following URL,

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-common-scenarios.html#CloudWatch-Agent-multiple-config-files

The Amazon CloudWatch agent is a software application that collects metrics and logs from various sources, including on-premises Linux servers. The agent uses configuration files to determine what metrics and logs to collect and where to send them.

To fetch application-specific metrics in addition to system metrics, the operations team can create a new configuration file with the appropriate settings. The question suggests that the new application is deployed on the same servers as the existing system, so the new configuration file should be appended to the existing configuration file.

There are two options for appending the new configuration file to the existing one: using aggregate-config or using append-config.

  • aggregate-config: This option creates a new configuration file with a different name and appends it to the existing configuration file. The new file contains only the settings for the application-specific metrics, and the existing file contains the settings for the system metrics. The agent aggregates the metrics from both files and sends them to CloudWatch.
  • append-config: This option creates a new configuration file with either the same or a different name and appends it to the existing configuration file. The new file contains the settings for the application-specific metrics, and the existing file contains the settings for the system metrics. The agent sends metrics from both files to CloudWatch separately.

Therefore, the correct answer to this question is B. Create a configuration file with a different file name and append it to the existing configuration file using append-config. This option allows the operations team to fetch application-specific metrics in addition to system metrics without disrupting the existing configuration.