...
When an application throws too many errors, an alert is raised. By default, when the error rate is above 5% an alert is sent by NewReloic.
Following the alert link gives information about the Error rate over the time period.
3.1 Connec Jobs
Background jobs can raise exceptions and when not caught, the job will be re-enqueued for future processing. This may lead to having a large amount of failing jobs being re-processed over many days.
Displaying the Events > Errors section gives a break down of the errors grouped by error message. Clicking on the message name will display the ruby trace to help troubleshoot the error. This will allow you to understand where the error comes from. Therefore, you may be able to solve it directly on your end. Otherwise, contact Maestrano support team and attach a screenshot of the new Relic error page, which will facilitate the resolution of the issue.
It is recommended handling errors in the application code and return error statuses rather bubbling up the entire stack trace.
Note that a public
Expanding the application backtrace will tell you which part of the code fails and needs to be fixed.
3.2 Connec API
Public endpoint will always be pinged by crawlers trying to find vulnerabilities and executable scripts. These types of requests should be blocked at the web server (nginx) level to avoid NewRelic raising 404 errors.
Sometimes public APIs are scanned for common scripts and return 404 errors, triggering alerts. These can be ignored.