Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upNeed for timestamp, because some sources may be with a latency #2308
Comments
This comment has been minimized.
This comment has been minimized.
|
Prometheus itself already supports this, however client libraries (and thus the cloudwatch exporter) do not pending #398 |
This comment has been minimized.
This comment has been minimized.
|
Hello, [root@prod-monitoring telegraf]# telegraf -config ./telegraf.conf -input-filter cloudwatch -test
[root@prod-monitoring telegraf]# date +%s The difference between the current date (1483095658) and the date reported by telegraf cloudwatch plugin (1483095000000000000) is roughly 10 minutes. So on the plugin side everything looks correct. |
brian-brazil
closed this
Mar 10, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
sbadan commentedDec 28, 2016
Hello,
I'm using Telegraf, Prometheus and Grafana integration. And we get some data from cloudwatch into telegraf.
The problem is that on cloudwatch the data appears with a ~10 minutes delay. But telegraf sends the data in the current moment, and it's written in the Prometheus this way. So we have 10 minutes old data displayed as current.
You can read here about the cloudwatch delay: https://help.datadoghq.com/hc/en-us/articles/203826415-Are-my-AWS-CloudWatch-metrics-delayed-
Would it be possible to implement data timestamp into Prometheus, so that we would somehow send the timestamp along with the data? Or maybe implement some time manipulations in the queries, so that we could retrieve the data series with the desired delay?