The OCID of the compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A user-friendly and mutable name suitable for display in a user interface.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}
A dictionary of HTTP request headers.
Note:* Monitors and probes do not support the use of the {@code Authorization} HTTP header.
The region where updates must be made and where results must be fetched from.
The OCID of the resource.
The monitor interval in seconds. Valid values: 10, 30, and 60. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Enables or disables the monitor. Set to 'true' to launch monitoring.
The optional URL path to probe, including query parameters.
The port on which to probe endpoints. If unspecified, probes will use the default port of their protocol. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
A URL for fetching the probe results.
A list of targets (hostnames or IP addresses) of the probe.
The RFC 3339-formatted creation date and time of the probe.
The probe timeout in seconds. Valid values: 10, 20, 30, and 60. The probe timeout must be less than or equal to {@code intervalInSeconds} for monitors. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
A list of names of vantage points from which to execute the probe.
This model contains all of the mutable and immutable properties for an HTTP monitor.