---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# HTTP response code check

# HTTP response code check {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Agent Client Collector provides the following additional check for HTTP
response code. This check is not associated with any policy.
{#http-response-code-check__table_k2q_bwj_g5b__entry__5}

| Type | Name | Description | Usage and usage example | Output |
|-|-|-|-|-|
| Event | util.check-http-response-code | Raises a critical event if the URL response code doesn't match the regex. Pass credentials (username and password) using secure parameters. | -u, --url  URL needs to be updated in the Monitoring HTTP Entrypoint/cmdb_ci_endpoint_http_list.do for the CI -r, --response-code  Regex string to match the response code. Otherwise, a critical event is raised. Default: 200 -f, --follow_redirects Follows redirect URLs Usage example: `command: check-response-code.rb -u 'https://servicenow.com' -r 2.. -f` | `CheckResponseCode OK : URL is in OK state. HTTP Response code is 200, matches regex` |
[Table 1. HTTP response code check]

{#http-response-code-check__table_k2q_bwj_g5b}