Hi Folks,I'm seeing alarms from url_response for response code 200which I assume is incorrect because the message says the request completed successfully.
Has anyone encountered something like this before or can share more insights around this.
url_response probe is calling cURL.
200 is response code that cURL has received.
But in my opinion this should not be an alarmurl_response Troubleshooting - CA Unified Infrastructure Management Probes - CA Technologies Documentation Describes 200 as an error code when Windows Authentication is enabled with the same message as I'm receiving.But in my case I do not use any Authentication and yet still I get the same error.
Could you please try increasing the dns_resolution_time in the alarm section of the probe configuration file should avoid the alert.
Alex YasudaTechnical Support | Enterprise Software Division
200 is a successful HTTP status code not an error code so no alarm should be generated.
This class of status codes indicates the action requested by the client was received, understood and accepted.
200 OKStandard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action
The url_response alarm message as currently defined:
<Failed> text = URL response for '$profile' failed. $code $description level = major subsystem = 1.1.14 token = failed variables = profile code description i18n_token = as#network.url_response.failed </Failed>
implies a failure/error.
In my opinion, no alarm should be generated for the 200 response. Despite the potential workaround, a support case should be opened, if not done so already, so an RFI can be entered/reported to Development. The probe is currently working as designed so perhaps an enhancement request (Idea) should be entered.