Skip to content

Investigate, document and propose ways to optimize CloudWatch API calls we make for cost #2913

@ravikesarwani

Description

@ravikesarwani

As part of monitoring of various AWS services we use CloudWatch API's (GetMetricData) to collect metrics data.
When users are using Elastic Agent to monitor various AWS services (metrics) they need to pay for the CloudWatch API calls.

This issue is to investigate the current code, do some testing, document the design and then propose various ways on how we can optimize the CloudWatch API calls we make so that our solution is as optimized as possible from end users cost perspective on total cost they need to pay.

Two outcomes we are trying to drive from this issue:

  • Define a use case (say we are collecting data for 100 EC2 instances) and explain our current code and how we use the CloudWatch API calls and the relation to cost. This forms the basis of explaining our current design.
  • Propose suggestions on how we can improve the API calls we make that would ultimately results in a reduced cost to the users, when monitoring using the Elastic Agent.

Implementation of specific proposal will be handled as separate new issues.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions