-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Metrics library - Changing metrics very small exponential number E-109 values to 0 #1106
Comments
Hello. I guess this depends how you actually report data to CloudWatch. Do you use a third-party reporter, parse a some servlet output or read out a |
I forgot to mention that we use Telegraf to pull the HTTP JSON metrics and write it to cloudwatch. In our case telegraf not able to convert the measurements , which is the bug confirmed by telegraf. So here is what recommened by telegraf team as a quick workaround. So looking for some guidance on what needs to be implemented on server to adjust the values to 0 before they enter in telegraf? Recommendations from Telegraf: [[inputs.httpjson]] |
I believe you use |
This issue is stale because it has been open 180 days with no activity. Remove the "stale" label or comment or this will be closed in 14 days. |
Hey, was there any progress on this? |
@abhi-jha This has to be fixed in your metrics reporter or in the monitoring system you're using. |
Hello,
we are using metrics library to pull the metrics from springboot apps. On pushing the metrics to AWS cloudwatch and whenever there is a small value found in metrics value like
(4.784335455263847E-109) cloudwatch rejects those values and breaks completely updating the other positive (>0) metrics too.
After spoke with AWS cloudwatch we found that these very smaller values (E-169) need to be converted to 0 before sending the same metrics to cloudwatch. Could we get some approach how to to modify these smaller values as 0 which is a solution that we are looking ?
Actual Behaviour:
com.sam.work.rest.controller.ServiceControllerV1.getData.oneMinuteRate:2.721723306412017E-169
2017-03-11T07:56:42Z E! Error writing to output [cloudwatch]: InvalidParameterValue: The value 0 for parameter MetricData.member.10.Value is invalid.
The value 0 for parameter MetricData.member.12.Value is invalid.
Desired Behaviour to resolve this issue:
com.sam.work.rest.controller.ServiceControllerV1.getData.oneMinuteRate:0
2017-03-14T22:15:51Z D! Output [cloudwatch] wrote batch of 74 metrics in 11.133616242s
Please refer the below link as explained by AWS rejecting those metrics lesser than E-109
http://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricData.html
The text was updated successfully, but these errors were encountered: