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 upFeat: recording rules linked to targets #3908
Comments
This comment has been minimized.
This comment has been minimized.
|
Dupe of #394 |
brian-brazil
closed this
Mar 4, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
roidelapluie commentedMar 4, 2018
Hi,
I would like to see the ability to add recording rules to jobs. Those recording rules would be run after each target of the job is scraped and would only be run on the metrics related to that target.
Use Case
We poll network switches every 5 minutes. It would be handy to be able to run irate() on each of the switches interfaces throughput.
Why not plain recording rules?
Plain recording rules would be run anywhere between scrapes and for all switches, thus taking a lot of time and getting "incorrect" timestamps.
Implications
It is not clear if we can easily know which metrics come from a specific target at the moment.