Recently, our team want to make use Shinken to monitor our services.
In our situation, we need to modify the configuration a little bit more.
Every time the configuration change we should user the reload function
provided by the Shinken init.d script which will turn out to stop arbiter
and start it again. a little bit more on reload of Shinken with this will
make arbiter unavailable for some time.
However, if we do not reload the configuration as soon as the configuration
changes we can lose some thing if the service is not OK. So, what schema
will mostly you chose to do a reload and what make you choose that schema.
:)
++++++
Ning Xie
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
