DOP-C02 · Question #396
A company hosts several applications in an AWS account. Each application sends logs to its own log group in Amazon CloudWatch. The company's CloudWatch costs for ingestion are increasing. A DevOps…
The correct answer is A. Use CloudWatch metrics to create a custom expression that identifies the CloudWatch log groups. You can leverage CloudWatch’s built‑in per‑log‑group metrics (for example, IncomingBytes) and use a metric‑math expression to rank or filter by the log groups that are ingesting the most data. This requires no additional instrumentation in your applications, no adhoc queries…
Question
A company hosts several applications in an AWS account. Each application sends logs to its own log group in Amazon CloudWatch. The company's CloudWatch costs for ingestion are increasing. A DevOps engineer needs to identify which applications are the source of the increased logging costs. Which solution will meet this requirement in the MOST operationally efficient way?
Options
- AUse CloudWatch metrics to create a custom expression that identifies the CloudWatch log groups
- BUse Amazon CloudWatch Logs Insights to create a query for the application log groups to identify
- CUse AWS Cost Explorer to generate a cost report that details costs for CloudWatch usage.
- DUse AWS CloudTrail to filter for CreateLogStream events for each application.
How the community answered
(21 responses)- A81% (17)
- B5% (1)
- C5% (1)
- D10% (2)
Explanation
You can leverage CloudWatch’s built‑in per‑log‑group metrics (for example, IncomingBytes) and use a metric‑math expression to rank or filter by the log groups that are ingesting the most data. This requires no additional instrumentation in your applications, no adhoc queries, and gives you a live dashboard of which log groups (and therefore which apps) are driving your ingestion costs.
Topics
Community Discussion
No community discussion yet for this question.