Managing Health Checks
Monitor the health of IP addresses and hosts using HTTP and ping monitors and on-demand probes.
Monitors, metrics, and probes that you create with the SDK, CLI, and API are associated with the region where you configure them. While using the API, you must perform monitor updates (including compartment changes), metrics retrieval, and probe results retrieval in the region where you configured them. However, you can list currently configured monitors and monitor details in every region, no matter where the monitors were configured.
Required IAM Policy
To use Oracle Cloud Infrastructure, you must be granted security access in a policy by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment to work in.
Administrators: For common policies that give groups access to Health Checks resources, see IAM Policies (on the Securing Health Checks page).
Following are the protocols available to use with monitors and on-demand probes.
Configure the monitored endpoint to accept the specified protocol.
- HTTP - Configure a GET or HEAD request using HTTP/1.1 to test the target for availability. Results (JSON) include the HTTP Status Code and DNS lookup, connection, and response timings. See HTTP Monitors and HTTP On-Demand Probes.
- HTTPS - Configure an encrypted HTTPS GET or HEAD request to test the availability of any secure hosted target. Default port: 443. Results (JSON) include the HTTP Status Code and DNS lookup, connection, and response timings. See HTTP Monitors and HTTP On-Demand Probes.
- ICMP - Configure an ICMP echo request ping. Results include the round-trip time (RTT) latency. See Ping Monitors and Ping On-Demand Probes.
- TCP - Configure a TCP handshake to the specified endpoint. Results include the round-trip time (RTT) latency. See Ping Monitors and Ping On-Demand Probes.Note
Because testing this connection can be costly, ensure that you own the endpoint.