MIME-Version: 1.0
References: <36c3f6d5-e869-4e0f-82e3-77cec8382c48@cmatte.me>
In-Reply-To: <36c3f6d5-e869-4e0f-82e3-77cec8382c48@cmatte.me>
From: Magnus Hagander <magnus@hagander.net>
Date: Wed, 20 Dec 2023 20:23:18 +0100
Message-ID: 
 <CABUevEyZyb30OKGGzwwb-QMc9bV2EP7exXWOSkDi4_qJKRakUQ@mail.gmail.com>
Subject: Re: pglister: monitor eximintegration queue with nagios?
To: =?UTF-8?Q?C=C3=A9lestin_Matte?= <celestin.matte@cmatte.me>
Cc: pgsql-www@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevEyZyb30OKGGzwwb-QMc9bV2EP7exXWOSkDi4_qJKRakUQ%40mail.gmail.com>
Precedence: bulk

On Wed, Dec 20, 2023 at 1:56=E2=80=AFPM C=C3=A9lestin Matte <celestin.matte=
@cmatte.me> wrote:
>
> Would it make sense to add eximintegration.queue to nagios/pglister_queue=
s.py?
>
> Currently, the nagios process checks a lot of different queues, but not t=
he eximintegration one. Would it make sense to add it?
> A while ago, I had issues with archives, and that would have allowed me t=
o detect them.
> Exim can also be monitored directly with nagios, but as there's already a=
 script to monitor all queues, that would simplify things.

I guess we could in theory, but I'd recommend monitoring that through
exim directly for a more up-to-date view (the eximintegration part is
cached). And it's perfectly normal to have quite a bit of queue of
outgoing emails pending even when things work perfectly right, so
alerting on it would have to be fairly adaptive anyway.

--=20
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/