Listing Results for an HTTP On-Demand Probe

List results for an HTTP on-demand probe in Health Checks.

On-demand probes are available through SDK, CLI, and API. 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.

  • This task can't be performed using the Console.

  • 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 [OPTIONS]

    For a complete list of flags and variable options 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. Get details for the HTTP on-demand probe.
      Review the response on creation. See Creating an HTTP On-Demand Probe.
    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.