-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MetricBeat] AWS module support wildcard format dimension value to reduce the metrics count #18050
Comments
dimension_names
to reduce GetMetric API Cost
Pinging @elastic/integrations-platforms (Team:Platforms) |
Thanks for creating this issue! Right now in CloudWatch metricset, we have a config parameter called
Maybe we should add support for using wildcard
With |
Yes , you are right, dimensions thanks for your reply. |
Will this improvement be added ? 😁 |
@kwinstonix Yes, sounds like a good enhancement to have! I will keep this issue open to track the work for enabling |
Is there any progress on this issue ? 🤔 |
@kaiyan-sheng , I have created a PR to implement this feature, could you help me review it? |
@kwinstonix Thank you and will do!! |
1. Describe the enhancement:
AWS CloudWatch metrics have many dimensions, for example, In
AWS/NetworkELB
namespace,UnHealthyHostCount
has the dimensions:When we query CloudWatch metrics with GetMetricData API, there are two metric.
If metricbeat could limit dimension names scope, after compared to
ListMetrics API
result, just one metric is retrived from AWS. so this can reduceAWS GetMetircData API
cost and metricbeat events amount.metricbeat will only make one metric query:
2. Describe a specific use case for the enhancement or feature:
3. reference
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html
https://github.com/prometheus/cloudwatch_exporter#cost
The text was updated successfully, but these errors were encountered: