[TNM] False alarms from pgBackRest events

[Matt]

Similar to [1], TnM is generating emails on INFO events logged in the
PostgreSQL logs by pgBackRest. These events do not have any of the INCLUDE
keywords, so I'm wondering if the format of the log entries is triggering
emails. Attempts with EXCLUDE have not prevented the false alarms. Changing
the log_line_prefix in postgresql.conf has also been unsuccessful.

Email example, note the event does not have a time zone (GMT) with the
timestamp as standard Postgres log entries do:

    [2] From A (lines 15418 - 15698)
2020-07-16 13:36:33.586 P00   INFO: pushed WAL file
'00000001000042C200000031' to the archive asynchronously
    2020-07-16 13:36:33.586 P00   INFO: archive-push command end: completed
successfully (5409ms)
    2020-07-16 13:36:33.630 P00   INFO: archive-push command begin 2.27:
[pg_wal/00000001000042C200000032] --archive-async --archive-timeout=90
--compress-type=lz4 --log-level-console=info --log-level-
[LINE TRUNCATED, original was 16,915 characters and 77 lines long]

tnm.config:

    LOG_LINE_PREFIX: %t P%p
    MAILSUBJECT: TnM - HOST Postgres errors UNIQUE : NUMBER

    INCLUDE: ERROR:
    INCLUDE: FATAL:
    INCLUDE: PANIC:
    EXCLUDE: canceling autovacuum
    EXCLUDE: INFO: archive-push
    EXCLUDE: INFO: pushed

    FILE1: /localdata/pgdata11/log/LATEST
    LASTFILE1: /localdata/pgdata11/log/postgresql-20200716_145958.log

[1] https://bucardo.org/pipermail/tnm/2018-August/000046.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://bucardo.org/pipermail/tnm/attachments/20200716/ec195ac1/attachment.htm>