-
-
Notifications
You must be signed in to change notification settings - Fork 330
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
[BUG] S3 bucket metrics are AWS 'region' dependent "NaN" #728
Labels
bug
Something isn't working
Comments
Any ideas, updates? Or is this 'cancelled due to lack of interest'? :-) |
I have also faced this bug. Is there any workaround or information on how to fix it?
|
Can you check again with v0.61.0 or newer? We faced the same issue, which has been resolved with v0.61.0. |
morremeyer
added a commit
to anaconda/alloy
that referenced
this issue
Sep 16, 2024
This bumps yet-another-cloudwatch-exporter to v0.61.0, which fixes [an issue with S3 metrics being reported as `NaN`](nerdswords/yet-another-cloudwatch-exporter#728). Affected metrics have a value of `0` in the scraped prometheus metrics. With the update to v0.61.0, they are reported correctly.
1 task
morremeyer
added a commit
to anaconda/alloy
that referenced
this issue
Sep 16, 2024
This bumps yet-another-cloudwatch-exporter to v0.61.0, which fixes [an issue with S3 metrics being reported as `NaN`](nerdswords/yet-another-cloudwatch-exporter#728). Affected metrics have a value of `0` in the scraped prometheus metrics. With the update to v0.61.0, they are reported correctly.
morremeyer
added a commit
to anaconda/alloy
that referenced
this issue
Sep 17, 2024
This bumps yet-another-cloudwatch-exporter to v0.61.0, which fixes [an issue with S3 metrics being reported as `NaN`](nerdswords/yet-another-cloudwatch-exporter#728). Affected metrics have a value of `0` in the scraped prometheus metrics. With the update to v0.61.0, they are reported correctly.
wildum
pushed a commit
to grafana/alloy
that referenced
this issue
Sep 17, 2024
* chore: bump yet-another-cloudwatch-exporter to v0.61.0 This bumps yet-another-cloudwatch-exporter to v0.61.0, which fixes [an issue with S3 metrics being reported as `NaN`](nerdswords/yet-another-cloudwatch-exporter#728). Affected metrics have a value of `0` in the scraped prometheus metrics. With the update to v0.61.0, they are reported correctly. * fixup! chore: bump yet-another-cloudwatch-exporter to v0.61.0 JobLevelMetricFields has been removed with nerdswords/yet-another-cloudwatch-exporter#1412 * fixup! chore: bump yet-another-cloudwatch-exporter to v0.61.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
Here is a snippet of data that is presented to our Prometheus for scraping:
eu-central-1
resident buckets are presented with "NaN" values.aws_s3_number_of_objects_maximum
.aws_s3_info
bucket metrics.Expected Behavior
All discovered buckets in all regions should present real numbers for scraping by Prometheus.
Steps To Reproduce
debug
to logging and can confirm that at least in the logs real number data is extracted from AWS CloudWatch - here is a snippet:Anything else?
The text was updated successfully, but these errors were encountered: