statusengine / worker

PHP worker process that writes all event data to a storage backend
https://statusengine.org/worker/#overview
GNU General Public License v3.0
9 stars 8 forks source link

Should UP/OK state always HARD state? #17

Closed nook24 closed 5 years ago

nook24 commented 5 years ago

I find it confusing that UP and Ok events are not always a HARD-State.

Related Issues: https://github.com/statusengine/worker/issues/16 https://github.com/naemon/naemon-core/issues/205

Is it a good idea to add an option like recovery_is_always_hard_state to the Statusengine Worker config.yml? option would affect the tables statehistory_host and statehistory_server, so an state=0 event would be always forced to be marked as hardstate.

nook24 commented 5 years ago

After thinking of this, this is a bad idea. Statusengine should not manipulate any data the were provided by the monitoring system.

http://www.naemon.org/documentation/usersguide/statetypes.html#example