We received a request to monitor a URL/API that always responds with a status 204 instead of 200 OK in case of success. As I see, url_response probe treats a 204 as a failure and creates an alarm. Is there a way/workaround to monitor such cases with the url_response probe?
API details that have to be monitored with url_response probe:
url_response message from a test of the url:
I also tried such settings as depicted below but we get an alarm anyway.
- expected result
Release : 20.3
Component : UIM - URL_RESPONSE
- url_response v1.35
In the url_response probe configuration, when Windows authentication is enabled and the web server processes the request but nothing is sent back, you will see an HTTP 204 error.
"Result: 204 The server has fulfilled the request, but there is no new information to send back."
The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional content to send in the response payload body
1: Create a nas pre-processing rule to ignore (exclude) the alarm.
2: Use the nas to create a new alarm (new_alarm) that is Informational, to replace the original alarm.
3: Deploy and use the e2e_appmon_dev probe on a dedicated workstation to access the website/url by recording a transaction script which gives you more control over the error/alarm handling.