Magnus Hagander wrote:
> On Mon, Jun 14, 2010 at 13:11, Bruce Momjian <bruce@momjian.us> wrote:
> > Magnus Hagander wrote:
> >> >> Seems like we need something like WARNING that doesn't cause the process
> >> >> to die, but more alarming like ERROR/FATAL/PANIC. Or maybe just adding a
> >> >> hint to the warning will do. How about
> >> >>
> >> >> WARNING: ?invalid record length at 0/4005330
> >> >> HINT: An invalid record was streamed from master. That can be a sign of
> >> >> corruption in the master, or inconsistency between master and standby
> >> >> state. The record will be re-fetched, but that is unlikely to fix the
> >> >> problem. You may have to restore standby from base backup.
> >> >
> >> > I am thinking about log monitoring tools like Nagios. ?I am afraid
> >> > they are never going to pick up something tagged WARNING, no matter
> >>
> >> If they are properly configured, I imagine they would. And if they're
> >> not, well, there's not much for us to do.
> >
> > What does that mean?
>
> It means that we can't prevent people from configuring their tools to
> ignore important warning. We can't prevent them rom ignoring ERROR or
> FATAL either...
My point is that most tools are going to look at the tag first to
determine the severity of the message, and might even have
log_min_messages set to ignore warnings. Esentially this message would
have to be special-cased for log filtering, and considering translation
issues, etc, it seems pretty odd.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ None of us is going to be here forever. +
