blob: 0f36803fe475f1a66b6efcc02d916d8a93737eca (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
### Understand the alert
This alert monitors the percentage of failed HTTP requests to a specific URL in the last 5 minutes. If you receive this alert, it means that your web service experienced connection issues.
### Troubleshoot the alert
1. Verify HTTP service status
Check if the web service is running and accepting requests. If the service is down, restart it and monitor the situation.
2. Review server logs
Examine the logs of the web server hosting the HTTP service. Look for any errors or warning messages that may provide more information about the cause of the connection issues.
3. Check network connectivity
If the server hosting the HTTP service is experiencing connectivity issues, it can lead to failed requests. Ensure that the server has stable network connectivity.
4. Monitor server resources
Inspect the server's resource usage to check if it is running out of resources, such as CPU, memory, or disk space. If the server is running low on resources, it can cause the HTTP service to malfunction. In this case, free up resources or upgrade the server.
5. Review client connections
It is also possible that the clients are having connectivity issues. Make sure that the clients are in a good network condition and can connect to the server without any issues.
6. Test the HTTP service
Perform HTTP requests to the service manually or using monitoring tools to measure response times and verify if the issue persists.
### Useful resources
1. [Apache Log Files](https://httpd.apache.org/docs/2.4/logs.html)
2. [NGINX Log Files](https://docs.nginx.com/nginx/admin-guide/monitoring/logging/)
3. [HTTP status codes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status)
|
