pfSense

Brilliant pfSense Dev Team!

Pushover service (like an all notifications services nowadays) HAS SEVERAL NOTIFICATION PRIORITY LEVELS: from low to critical.

So, FROM PFSENSE USER VIEW would be logically right to receive notifications with different levels, for example:

Suricata / Snort rules SUCSESSFULY UPDATE - that’s normal, but error in rules update - may be Hi/Critical (as User it set in settings).

Error with uploading pfSense’s configs by ACB on Netgate’s servers - are Hi/Critical, but successfully complete uploading operation - not need much attention, so Low priority.

So, the making Pushover integration where ALL NOTIFICATIONS DROPPED IN ONE STREAM WITH ONE LEVEL (like now are) - REALLY UNUSABLE, because after 1-2-3 day Your Pushover app would be filled with a ton of messages. And this make this integration unusable and out of sense.

Also from developer point of view I understand that because a lot of extra pfSense packages are made by community or independent maintainer, would be near impossible to changing the package logic.
And also make this huge work and after that found that Pushover services died/acquisited by someone else and will work need to be done again - also not good.

So the better way to work with Pushover (and any other integration service later in coming years) would be:

make cronjob that parsing system logs and certain package logs, and if found words “error” (for example), -> sending to notification services (Pushover in our case) notification WITH APPROPRIATE LEVEL (HI/CRITICAL).

In this case:
- THE LEVEL OF EVENT = LEVEL OF NOTIFICATION;
- pfSense not hard depending on certain notifications service and future changes or adding other notifications services are possible and easy;

Sound reasonable, yet?