We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Parser is gathering the metric timestamp here: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/prometheus/parser.go#L89
But then it gets ignored and the current time is used instead: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/prometheus/prometheus.go#L148
When I expose a prometheus metric with a timestamp like the example:
# HELP test_metric Metric read from /tmp/node_exporter/textfile/test_metric.prom # TYPE test_metric untyped test_metric{label="value"} 1.0 1490802350
I expect the test output to be something like the example:
test_metric,label=value,url=http://localhost:3002/metrics value=1.0 1490802350000000000
The output timestamp uses the current time
test_metric,label=value,url=http://localhost:3002/metrics value=1.0 1490809413000000000
The text was updated successfully, but these errors were encountered:
@djjorjinho Should be an easy fix now that you have it all figured out, do you want to make up a PR?
Sorry, something went wrong.
@danielnelson I've created #2596
No branches or pull requests
Parser is gathering the metric timestamp here:
https://github.com/influxdata/telegraf/blob/master/plugins/inputs/prometheus/parser.go#L89
But then it gets ignored and the current time is used instead:
https://github.com/influxdata/telegraf/blob/master/plugins/inputs/prometheus/prometheus.go#L148
Expected behavior:
When I expose a prometheus metric with a timestamp like the example:
I expect the test output to be something like the example:
Actual behavior:
The output timestamp uses the current time
The text was updated successfully, but these errors were encountered: