-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False alarms from pgBackRest events #35
Comments
|
Experimenting with making the Postgres log line prefix similar (%m) and the tail_n_mail timezone regex optional: master...kmatt:2.8.1-pgbackrest Ideally changing the server log format would not be necessary. |
The pgbackrest lines do not parse because they do not respect log_line_prefix and just write their own format, which is a little rude. For now, --skip_non-parsed is indeed the best solution, but I will look into something better. |
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, because the example below reporting LINE_TRUNCATED.
Attempts with EXCLUDE have not prevented the alerts. Changing the log_line_prefix in postgresql.conf has also been unsuccessful.
For example, note the event does not have a time zone (GMT) with the timestamp as standard Postgres log entries do (
2020-07-16 15:00:04 GMT
...), this is an email from tail_n_mail, where there are no error conditions in the log:tnm.config:
[1] https://bucardo.org/pipermail/tnm/2018-August/000046.html
The text was updated successfully, but these errors were encountered: