Repository navigation
Notification issues #425
|
I've configured the email notifications for a number of things including backups and host backups and the daily digest. Those I'm not getting although test works and I do get alerts on things like utilization, invalid logins, etc. |
Replies: 4 comments 1 reply
|
Hi, thank you for reporting this. Those three do not travel the same way as the alerts you are receiving, which is why the test and the usage alerts work while they don't:
It would also help to know your ProxMenux version, and whether Settings → Notifications → History shows any backup entry. |
|
Hi @sahartford, thanks for checking those, and sorry for the wait. Host backups. You were right that HTTPS wasn't your case. Going through it again I found the actual reason. The Monitor treated "host backup complete" as the same event every time and left 24 hours between two identical notifications, so a job that runs every night kept falling inside that window. On top of that, on a channel with the daily digest enabled the result was kept for the digest instead of being sent when the job ended. What I told you before, that backups are sent right away, was true for VM and CT backups but not for host backups. Both are corrected in the development branch: every run of a host backup is now sent when it ends, like a VM or CT backup. It will be in the 1.2.7 version. VM and CT backups. Good to hear that one is sorted. Daily digest. It is only sent on days when at least one informational event was held for it, for example an LXC update that completed. Warnings, errors, backups and VM or CT starts and stops are sent live and never go into it, so on a quiet host there can be several days with nothing to summarise, and then no email is sent. Each run is recorded, though: Settings → Notifications → History shows a digest entry for every day, saying whether it had something to send. If those entries are there, the schedule is working. |
|
Thanks for the update. Re: Daily Digest, you mention checking "Settings -> Notifications -> History". I don't have/see that section. |
|
Hi @sahartford, sorry, I told you it would be there in the next version, but it didn't make it into this beta. It will be available in the next stable version, which is coming out very soon. If you want to check it now, you can do it from the host's shell. This only reads the history, it doesn't change anything: python3 -c "import sqlite3; c = sqlite3.connect('file:/usr/local/share/proxmenux/health_monitor.db?mode=ro', uri=True); [print(*r) for r in c.execute("SELECT sent_at, channel, success, message FROM notification_history WHERE event_type = 'digest' ORDER BY id DESC LIMIT 10")]" Each line is one day's digest run for a channel. If you see a line for each day, the schedule is working as it should. |
Hi @sahartford, sorry, I told you it would be there in the next version, but it didn't make it into this beta. It will be available in the next stable version, which is coming out very soon.
If you want to check it now, you can do it from the host's shell. This only reads the history, it doesn't change anything:
python3 -c "import sqlite3; c = sqlite3.connect('file:/usr/local/share/proxmenux/health_monitor.db?mode=ro', uri=True); [print(*r) for r in c.execute("SELECT sent_at, channel, success, message FROM notification_history WHERE event_type = 'digest' ORDER BY id DESC LIMIT 10")]"
Each line is one day's digest run for a channel. If you see a line for each day, the schedule is working a…