-
Notifications
You must be signed in to change notification settings - Fork 31
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
Support evaluating metrics and switching states #2162
Comments
false from the expressions will just be ignored. We'd add a few functions to allow looking up data etc The data layer should get a new hook where these watchers can register for updates so they will get notified if data changes and also when they enter the matching states. It will also check on interval to cater for external updates to data We'd need some flip-flop or true-if-already-true induced repeated transitions. Typically I think such a watcher would be sat on |
Watcher can be used to flip states based on the contents of data, facts and more Signed-off-by: R.I.Pienaar <[email protected]>
Watcher can be used to flip states based on the contents of data, facts and more Signed-off-by: R.I.Pienaar <[email protected]>
Signed-off-by: R.I.Pienaar <[email protected]>
(#2162) Consistency update with other watchers
To deliver on the hopes of reacting to metric values we'd need to initiate state changes.
I imagine you could add some queries to the metric watcher using expr and based on their boolean returns you'd do success/fail transitions.
Today we support storing the metrics to machine data (#2157) but I'd like to eventually improve on that by storing in a small localised tsdb, think hours of data not days, so that expr functions can do things lke average over recent metrics etc
But we can start with just the stored data for now
The text was updated successfully, but these errors were encountered: