You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2019. It is now read-only.
Currently there are 3 components to generating a notification for issues raised by satellite:
Grab a metric specified in recipes.clj
Publish a condition if the metric meets some threshold criteria specified in a json file (called a comet I think)
Determine how to handle the condition (notification mechanisms, automated resolution actions, etc.) in riemann-config.clj on the satellite-master.
Unfortunately, adding a new metric (step 1 above) requires that we change the recipes.clj file in the satellite-slave. In order to deploy the change we need to recompile the jar, which is not ideal. It would be nice if the recipes could be stored outside of the jar.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently there are 3 components to generating a notification for issues raised by satellite:
Unfortunately, adding a new metric (step 1 above) requires that we change the recipes.clj file in the satellite-slave. In order to deploy the change we need to recompile the jar, which is not ideal. It would be nice if the recipes could be stored outside of the jar.
The text was updated successfully, but these errors were encountered: