Oracle Cloud Infrastructure Documentation

Listing Results for an HTTP Monitor

List results for an HTTP monitor in Health Checks.

Results are available a few moments after you create the monitor or on-demand probe. Each result includes the monitoring location (target), vantage points, endpoint availability, and test timestamp.

    1. On the Health checks list page, select the name of the HTTP monitor that you want to work with. If you need help finding the list page or the HTTP monitor, see Listing HTTP Monitors.
    2. On the HTTP monitor's details page, select Health check history
      The past 90 days of results are available.
    3. To view details for a result, expand it.

    Filtering List Results

    Use filters to limit the results in the list. Perform one of the following actions depending on the options that you see:

    • From the Search and Filter box above the list table, select one or more filters and specify the values that you want to use to narrow the list. In general, the filters correspond to the columns shown in the list table, although some filters represent attributes that aren't shown in the table. The Compartment filter is always displayed next to Applied filters.
    • On the left side of the list page, select a value from one of the available filters, such as compartment, state, or tags.

    Change the order of the items in the list table by using the sort icons next to the column names.

    For information about searching for resources and managing the columns in the list table, if those features are available, see Listing Resources.

  • Use the oci health-checks http-probe-result list command and required parameters to list results for an HTTP monitor or on-demand probe:

    oci health-checks http-probe-result list --probe-configuration-id <http_monitor_or_probe_OCID>

    For a complete list of parameters and values for CLI commands, see the CLI for Health Checks.

  • Run the ListHttpProbeResults operation to list results for an HTTP monitor or on-demand probe.

    Example Responses

    Following is an example healthy response.

    {  
  "key": "<uniqueid>",
  "probeConfigurationId": "ocid1.httpmonitor.OC2..<unique_ID>",
  "compartmentId":"ocid1.compartment.oc1..<unique_ID>",
  "connection": {
    "address": "93.184.216.34",
    "connectDuration": 114,
    "port": 443,
    "secureConnectDuration": 99
    },
  "connectEnd": 1517323711649,
  "connectStart": 1517323711535,
  "dns":{
    "domainLookupDuration": 29,
    "addresses": [
      "93.184.216.34",
      "2606:2800:220:1:248:1893:25c8:1946"
      ]
    },
  "domainLookupEnd": 1517323711534,
  "domainLookupStart": 1517323711505,
  "duration": 171,
  "encodedBodySize": 1270,
  "fetchStart": 1517323711505,
  "isHealthy": true,
  "isTimedOut": false,
  "protocol": "HTTPS",
  "requestStart": 1517323711649,
  "responseEnd": 1517323711676,
  "responseStart": 1517323711673,
  "secureConnectionStart": 1517323711550,
  "startTime": 1517323711505,
  "statusCode": 200,
  "target": "www.example.com",
  "vantagePointName": "dgo-nyc"
}

    Following is an example unhealthy response.

    {  
  "key": "<uniqueid>",
  "probeConfigurationId": "ocid1.httpmonitor.OC2..<unique_ID>",
  "compartmentId":"ocid1.compartment.oc1..<unique_ID>",
  "connection": {
    "address": "203.0.113.1",
    "port": 80
    },
  "dns":{
    "domainLookupDuration": 0,
    "addresses": []
    },
  "domainLookupEnd": 0,
  "domainLookupStart": 0,
  "errorCategory":"TRANSPORT",
  "errorMessage":"TCP Ping Connection Error: dial tcp 203.0.113.1:80: connect: no route to host",
  "icmpCode": 0,
  "isHealthy": false,
  "isTimedOut": false,
  "latencyInMs": 0,
  "protocol": "TCP",
  "startTime": 1517323711505,
  "target": "www.example.com",
  "vantagePointName": "dgo-nyc"
}

    Send an API Request to the Results URL

    1. On the Health checks list page, select the name of the HTTP monitor that you want to work with. If you need help finding the list page or the HTTP monitor, see Listing HTTP Monitors.
    2. Find the results URL from the details.
      Example results URL for a ping monitor: 
      "resultsUrl":"http://healthchecks.us-ashburn-1.oraclecloud.com/20180501/pingProbeResults/ocid1.pingmonitor.oc1..<uniqueid>"
    3. Send a signed API request to the results URL.
      The request must be signed to provide authentication information.