DX Unified Infrastructure Management

  • Private Community

  • 1.  url response alerts on response code 200

    Posted Jan 09, 2019 05:58 AM

    Hi Folks,

    I'm seeing alarms from url_response for response code 200
    which 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.



  • 2.  Re: url response alerts on response code 200

    Broadcom Employee
    Posted Jan 09, 2019 06:11 AM

    url_response probe is calling cURL.

    200 is response code that cURL has received.

     



  • 3.  Re: url response alerts on response code 200

    Broadcom Employee
    Posted Jan 09, 2019 06:12 AM


  • 4.  Re: url response alerts on response code 200

    Posted Jan 09, 2019 07:13 AM

    But in my opinion this should not be an alarm
    url_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.



  • 5.  Re: url response alerts on response code 200

    Posted Jan 09, 2019 07:40 AM

    Sinab,

     

    Could you please try increasing the dns_resolution_time in the alarm section of the probe configuration file should avoid the alert.

     

    Kind Regards,

     

    Alex Yasuda
    Technical Support | Enterprise Software Division

     

    Broadcom



  • 6.  Re: url response alerts on response code 200

    Broadcom Employee
    Posted Jan 09, 2019 11:03 AM

    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 OK
    Standard 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

     

    http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml 

     

    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.

     

    Steve