Then an admin might miss the original log, if out of it's browsing window. However I agree the log could be done at a lower pace: - Check every minute, log directly upon status change - Otherwise re-log current status every 30 minutes
On 12/02/2020 17:48, Antoine Duprat wrote: > Shouldn't it be more logic to log only status changes ? > > I mean, if you are in a degraded state, you will log the same thing each > minute else if you have fixed the issue. > > Le mer. 12 févr. 2020 à 11:43, Tellier Benoit <btell...@apache.org> a > écrit : > >> +1 >> >> We should make this happen. >> >> On 12/02/2020 17:29, Matthieu Baechler wrote: >>> On Wed, 2020-02-12 at 16:27 +0700, Tellier Benoit wrote: >>> >>>> - Through grafana, the admin will have the information directly >>>> available. Nowaday, health-checks requires her to execute the >>>> healthcheck via webadmin. More actions is generally the best way of >>>> having none of them taken. >>>> >>> >>> I just want to add, on that matter, that I already proposed to have a >>> timer that logs health state to WARN when status is `degraded` and >>> ERROR when status is `down` on a sensible time interval (like once a >>> minute) and that would be enabled in our default configuration. >>> >>> That way the logs, which are the first and most basic tool any admin is >>> looking at, would give you that very important information. >>> >>> Cheers, >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org >> For additional commands, e-mail: server-dev-h...@james.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
