no token found on elb sum metrics about yet-another-cloudwatch-exporter HOT 6 CLOSED

@tsupertramp just let me know what you think is the best approach to make this work, I'm happy to create a PR then :)

from yet-another-cloudwatch-exporter.

Sorry for the late reply. Combination of sickness and vacation.

Wow interesting phenomenon - No quick idea.

I want to merge two prs the next days. I will look into that during these contribution hours as well.

Could you in the meantime please try out the following config:

          - name: HTTPCode_Backend_5XX
            statistics:
              - 'Sum'
            period: 300
            length: 300
            nilToZero: true
            disableTimestamp: true

from yet-another-cloudwatch-exporter.

No worries at all, hope you feel better now.

Indeed just using period: 60 & length: 300 seems to fix the problem. Maybe the length: 900 causes some parser issues for some reason.

from yet-another-cloudwatch-exporter.

Will fix this issue. As it throw an error instead of throwing errors during scraping.

I think we should warn the user that elb metrics are only available for 5m. I think the period of 60 is the problem in your case. As it is not possible to get values for 1m.

Not sure why it does not throw an error but i will find out.

from yet-another-cloudwatch-exporter.

disableTimestamp is default in next release. This was probably caused by this.

Closing this issue here.

from yet-another-cloudwatch-exporter.

awesome, thank you :)

from yet-another-cloudwatch-exporter.