-
Notifications
You must be signed in to change notification settings - Fork 12
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
Send state_id over time to have availability #23
base: refactored
Are you sure you want to change the base?
Conversation
You should make this feature configurable in the module configuration file. Sending state for all hosts and services may be overloading an installed Graphite instance ... |
In graphite2.cfg, options are: state_enable 1 shinken-monitoring#1=enable send state / 0=disable state_host 1 shinken-monitoring#1=enable send state for host / 0=disable state_service 1 shinken-monitoring#1=enable send state for service / 0=disable
Thx for your suggestion. I added some options to enable or disable this feature and you will be able to choose sending state for all hosts OR\AND all services. I am agree with you "Sending state for all hosts or\and all services may be overloading" for Graphite. Other suggestions are welcome. |
+1 for the options. I think that this feature should be disabled as default. Nice idea to send the state only if it changed. As of my memory, you can easily know if the state chaned thanks to the received brok data ... you should find a state and a last_state information in the brok data :) |
So, I disabled this feature as default. |
This Pull request send availability for hosts and services in Graphite over time.
It's useful to see when an host/service is down over time.
How it's works ?
The broker receive all data from all check. A function for host read data about state and other function do same for service.
For HOSTS i added:
Same logic for services
The result with Grafana and Graphite as datasource