...
From there an investigation will have to be lead to find the root cause of the performance issue and address the underlying problem.
See https://maestrano.atlassian.net/wiki/x/gOTgBQ
Error Rate
When an application throws too many errors, an alert is raised. Following the alert link gives information about the Error rate over the time period.
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.
It is recommended handling errors in the application code and return error statuses rather bubbling up the entire stack trace.
Note that a 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.