Can I use custom HTTP response codes with IPNetwork Monitor?
Q: My Web application can return custom HTTP response codes. How can I set up IPNetwork to treat these codes as acceptable and set up required actions for them?
A: In the HTTP(S) monitor settings you may specify a list of HTTP response codes. Generally, all server response codes starting with 400 are considered errors. If the server replies with such a response code, the resource being requested is considered unavailable and the monitor enters the Down state.
You can list the acceptable response codes for both Down and Warning states in the corresponding sections on the monitor’s State Conditions tab:
If you need more fine grain behaviour, you can use Script or Program monitors to invoke external custom script or program which would use the returned HTTP response code as monitor performance value (see Script or Program Monitor parameters).
Create Script or Program monitor and configure it. Script can be customized to switch monitor to one of the OK, Down and Warning states depending on the HTTP response code, and notifications may be configured to be sent upon entering and exiting from any of these states.
Related topics
Check out our Knowledge Base where we answer questions regarding various topics. Set acceptable response codes for Warning and Down states on the HTTP(S) monitor State Conditions tab. Generally yes. Server response codes starting with 400 are treated as unavailable unless the monitor settings list a code as acceptable. Use a custom script or program when response-code handling needs more detailed OK, Warning, and Down logic than the HTTP(S) monitor settings provide.
Frequently Asked Questions
Where are acceptable HTTP response codes configured?
Are all HTTP 400-level responses treated as errors by default?
When should a Script or Program monitor be used for HTTP response codes?