Requests | Blesta

Requests

System Issue Email Notifications

Alk shared this idea 3 years ago
Under Consideration

It would be extremely helpful to have an email notification to the admin when there are any Blesta system issues, rather than relying on the system status widget in the staff portal. Not everyone checks the staff portal daily (there isn't necessarily a need, particularly if you are a small business and you use the support tickets via email) and, for example, the crons can get stuck and therefore it can go unnoticed that there is an issue. If you don't have a lot of business, you can't rely on the fact that you haven't heard from anyone in a while..

Comments (4)

photo
1

I like the idea, but it's not very simple to implement. A simple solution would result in staff getting spammed every time an incident occurs. A more measured approach is to log these kinds of issues, and then send out a single digest email once a day or at some interval to staff who are subscribed to receive those notices.

The good news is that with 4.1 comes monolog, which means there is a common place that issues are starting to be logged to. Over time, monolog will handle more and more logging, and some type of staff notification system will be feasible.

photo
1

Have this happened though or what's it progress? Thanks to an Cron Job Erroring Out for Downloading Tickets I didn't know I haven't actually responded to the client for over a day now. :(

photo
1

Easy:

-> first visitor of the hour/day that sends a http-request to blesta causes an event that picks up critical/warn entries from the logfile and mails it to a specified e-mail address.

-> log timestamp of notification sent.

=> repeat

photo
1

A great suggestion by @Sebastian on implementation there!

So the original reason for me requesting this feature was for the exact reason that you experienced @Ricky Torres, ie. that the Cron would error and not download the tickets via POP...and it would go unnoticed. Over time I found that the reason for the Cron occasionally erroring like this was because there was a communications error with the remote POP server at the time that the Cron was polling the remote POP server. Naturally, this communications error would be transitory and so it would be difficult to troubleshoot.

My solution was to move the mailbox onto the same server where Blesta was hosted (so it was no longer a remote POP server) and the problem then resolved itself and the Cron no longer errored when downloading tickets. I've had no problems to my knowledge since doing this. I suspect that a lot of Blesta users use the PIPE tickets option and therefore this also eliminates this Cron issue (this is another option for you).

As a backup, I also use Zapier to send me a weekly (or it could be a daily) email to a specified "test ticket" to ensure that the downloading of tickets is still working.

Hope this helps.

photo