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 upRecording Rules take more time in Prometheus 2.3.0 after upgrade #4871
Comments
This comment has been minimized.
This comment has been minimized.
|
Can you share the recording rules and the definition of the firing alerts? |
simonpasquier
added
component/rules
kind/more-info-needed
labels
Nov 16, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dhbarman commentedNov 15, 2018
Proposal
Use case. Why is this important?
Prometheus recording rules should not take more time
Bug Report
What did you do?
Upgraded Prometheus 2.2.1 to 2.3.0. The same set of recording rules were taking less time with previous version.
What did you expect to see?
Alarms based on metrics (recording rule evaluation) should not have gotten fired.
What did you see instead? Under which circumstances?
We are observing alarms firing.
Environment
System information:
Linux 4.1.12-124.19.7.el7uek.x86_64 x86_64
Prometheus version:
prometheus, version 2.3.0 (branch: heads/v2.3.0, revision:
290d717)
build user: teamcity@tca-hv05-agent018-default
build date: 20181030-04:34:03
go version: go1.11.1