Skip to content
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

prometheus_rule_group_last_duration_seconds is in ms? #5149

Closed
sepich opened this Issue Jan 29, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@sepich
Copy link

sepich commented Jan 29, 2019

Bug Report

What did you do?
We're using alerts with prometheus_rule_group_last_duration_seconds.

What did you expect to see?
In v2.6.1 it was 0.005921854 which seems like seconds

What did you see instead? Under which circumstances?
Starting with 2.7.0 it start to return too large values

# HELP prometheus_rule_group_last_duration_seconds The duration of the last rule group evaluation.
# TYPE prometheus_rule_group_last_duration_seconds gauge
prometheus_rule_group_last_duration_seconds{rule_group="/etc/prometheus-shared/rules/app.yml;app"} 1.417883e+06

so rules are failing now:
prometheus_rule_group_last_duration_seconds/prometheus_rule_group_interval_seconds now in thousands

Environment

  • System information:

Linux 4.9.0-8-amd64 x86_64

  • Prometheus version:
prometheus, version 2.7.0 (branch: HEAD, revision: 410ee9e04acb8f59f400858752ca82b4ef88035e)
  build user:       root@3bc81b516055
  build date:       20190128-10:09:51
  go version:       go1.11.5
@codesome

This comment has been minimized.

Copy link
Member

codesome commented Jan 30, 2019

Can confirm this is a bug

g.metrics.groupLastDuration.WithLabelValues(groupKey(g.file, g.name)).Set(float64(dur))
- I don't see it being changed to seconds here.

@cstyan

This comment has been minimized.

Copy link
Contributor

cstyan commented Jan 31, 2019

@codesome this too, looks like the automatic closes #issue isn't working?

@simonpasquier

This comment has been minimized.

Copy link
Member

simonpasquier commented Feb 1, 2019

@cstyan when the fix isn't made against master, GitHub doesn't auto-close the issue...

@cstyan

This comment has been minimized.

Copy link
Contributor

cstyan commented Feb 1, 2019

Oh, didn't know that! Thanks @simonpasquier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.