Overview of the Health Checks Service

The Oracle Cloud Infrastructure Health Checks service provides users with high frequency external monitoring to determine the availability and performance of any publicly facing service, including hosted websites, API endpoints, or externally facing load balancers. By using Health Checks, users can ensure that they are immediately aware of any availability issue affecting their customers.

Health Checks Service Components

The following list describes the key components used in creating a health check.

Monitors allow you to continuously monitor the health of public-facing endpoints. You can configure monitors to use either HTTP and ping protocols. Monitors are classified as either Basic or Premium, based on the configured test interval. A monitor is considered Premium if the test interval is set to 10 seconds, and considered Basic if the test interval is greater than 10 seconds. Behavioral differences do not exist between a Basic and Premium monitor, other than the frequency that the monitor is run.
On-demand probes allow you to run a one-time probe to assess the health of a public-facing endpoint. You can configure on-demand probes to use either or both HTTP and ping protocols. This feature is only available through the REST API. A limit exists on how many on-demand probes can be run in a 24-hour period. On-demand credits are consumed as the probes are run, and replenished gradually over time.
Vantage points are geographic locations from which monitors and probes can be run to your specified target. Oracle Cloud Infrastructure maintains dozens of vantage points around the world.
The Health Checks service allows you to configure both HTTP and ping type monitors. Each type has respective protocols.

Ways to Access the Health Checks Service

You can access Health Checks using the Console (a browser-based interface) or the Health Checks REST API. Instructions for the Console and API are included in topics throughout this guide.

To access the Console, you must use a supported browser. To go to the Console sign-in page, open the navigation menu at the top of this page and click Infrastructure Console. You are prompted to enter your cloud tenant, your user name, and your password.

Authentication and Authorization

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

An administrator in your organization needs to set up groups , compartments , and policies  that control which users can access which services, which resources, and the type of access. For example, the policies control who can create new users, create and manage the cloud network, launch instances, create buckets, download objects, etc. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see Policy Reference.

If you’re a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.

Health Checks Service Capabilities and Limits

The Oracle Cloud Infrastructure Health Checks service is limited to 1000 endpoint tests per account.

See Service Limits for a list of applicable limits and instructions for requesting a limit increase. To set compartment-specific limits on a resource or resource family, administrators can use compartment quotas.

Required IAM Service 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.

If you're new to policies, see Getting Started with Policies and Common Policies.

Administrators: For common policies that give groups access to Health Checks resources, see IAM Policies (Securing Health Checks).

Moving Health Checks to a Different Compartment

You can move health checks from one compartment to another. When you move a health check to a new compartment, its associated monitor and test results moves with it. After the move, health checks are accessible through the SDK, CLI, and Console. For more information, see Managing Compartments.

Tagging Resources

You can apply tags to your resources to help you organize them according to your business needs. You can apply tags at the time you create a resource, or you can update the resource later with the wanted tags. For general information about applying tags, see Resource Tags.


Learn about security for Health Checks.

For information about how to secure Health Checks, including security information and recommendations, see Securing Health Checks.