Settings service: timeout to avoid `--save`

[Krysztophe]

After the settings service triggers an alert, it must be reset with --save.

It is a tedious manual operation, and more complicated with named accounts different from the monitoring account (rights to manage and so on).

Idea: adopt the same behaviour as in the uptime service,
and add a timeout in --warning (eg 2d).

So, after a parameter change, the service would reset itself after some duration. From Icinga, it would be only necessary to ack the service.

BTW, the service never raises a Critical although the doc says so, and the code seems to hint that it was supposed to raise a Critical when a restart is pending. This last status should not be cleared; it will become a simple Warning after the restart, and clears itself if the timeout is set.

[gleu]

Sounds like a great idea to me. Keen to write a patch for this?

[Krysztophe]

I have no time for this, but this bugs me enough that I'll probably postpone something more important.

[blogh]

I'll try to do it this week.

[blogh]

I'll use the critical threshold since the service returns only that.