Add timer next trigger #181
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This metric shows next time a timer will fire. Care has been taken to handle real-time and monotonic timers correctly. Real-time timers return their value directly as a Unix timestamp as microseconds. The only special case is when the corresponding service is running, the timestamp is the max unit64 value. We filter those values out. Monotonic timers return the next time a service will run as the number of microseconds since the system boot time. Some computation is needed to get the next time as a standard Unix timestamp. Signed-off-by: ibizaman <ibizaman@tiserbox.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This metric shows next time a timer will fire.
Care has been taken to handle real-time and monotonic timers correctly.
Real-time timers return their value directly as a Unix timestamp as microseconds. The only special case is when the corresponding service is running, the timestamp is the max unit64 value. We filter those values out.
Monotonic timers return the next time a service will run as the number of microseconds since the system boot time. Some computation is needed to get the next time as a standard Unix timestamp.
I had great success using it to create a backups dashboard and alert in ibizaman/selfhostblocks#588. There are some screenshots here https://shb.skarabox.com/blocks-monitoring.html#blocks-monitoring-backup