Onboarding nginx: alerting #1864
Description
This should be the last chapter of the onboarding for nginx.
A couple examples I have found in some old blogs are:
- Alerting on a spike in error logs for a certain resource may mean we have deleted a resource that is still needed.
- Reviewing access logs to see when a services peak times are (and therefore when it might be best to perform things like maintenance).
- Alerting on a sudden spike in client requests may point to something malicious (like a DDoS attack).
These could be tied in with the ML docs to discuss alerting when anomalies are found as well.