-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
Notify Admins that page errors exist even when using dynamic callbacks #1392
Comments
I thought about this one, and for a minute, I thought to myself, who cares it's the GUI. It's going to be tricky though. We may never know which plugin per se as plugins can inject code just about anywhere. |
That is quite true. Unless there is a backtrace in the output. |
I would rather see the error log of the syntax error. So, a callback to indicate that there was a problem with such and such a page is a better idea. Has to be a global link though, which is the bitch -1 realm. |
Then have an Admin Error Email based upon that Callback. |
AJAX handled errors do not notify Admins that page errors exist
Turned this into a detection for 500 or better and will send an Administrative email and log a Cacti error when it occurs. |
Slow the number of Emails if you have a page error to once every two hours per error page.
If a plugin is clicked on, an AJAX error is correctly handled if error 500 occurs. However, the plugin itself is not disabled and there is no evidence of the error 500 in the Cacti log since it occurs before Cacti can even start.
Have a simple API page to receive a single name of the plugin to disable (with validation code?) which can be called without checking the status from the jQuery HTTP error handler if /plugins/ is detected in the url.
The text was updated successfully, but these errors were encountered: