...
The web transaction time is stable over time and the APDEX is acceptable. The application behaves correctly and no actions is required.
2 - CPU Alerts
Under heavy application load, CPU can raise alerts and should be closely looked into. CPU reaching 100% usage leads to applications behaving slowly and becoming unresponsive.
These alerts require immediate action:
- Check the transactions response time and APDEX
- If the application becomes slow or unresponsive, it will need to be restarted
- Investigate the root cause, this will require profiling of the application
- Check if we had an usual application load over this period of time
3 - APDEX Alert
The APDEX score is based on the application response time, when the application performs slowly, an alert is raised.
...
From there an investigation will have to be lead to find the root cause of the performance issue and address the underlying problem which is performance related.
See Application Performance Monitoring (APM)
...
4 - Error Rate
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.
...
4.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.
...
Expanding the application backtrace will tell you which part of the code fails and needs to be fixed.
...
4.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.
...