ORACLE CLOUD

Monitoring actions

15 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.

Every Monitoring action

  • OCI Monitoring: Create AlarmCreate an alarm from an MQL query over a metric namespace. When the query breaches for the pending duration, the alarm fires to its destinations (Notifications topic OCIDs). Severity is CRITICAL/ERROR/WARNING/INFO.
  • OCI Monitoring: Create Alarm SuppressionMute an alarm for a scheduled window (e.g. a planned maintenance outage). The alarm is suppressed at ALARM level between the from/until times so it will not fire. Times are RFC3339.
  • OCI Monitoring: Delete AlarmDelete a Monitoring alarm by its OCID. This stops the alarm from evaluating and firing: it is permanent and synchronous.
  • OCI Monitoring: Delete Alarm SuppressionDelete an alarm suppression by its OCID, lifting the silence it applied to the alarm. Synchronous: the suppression is removed immediately.
  • OCI Monitoring: Get AlarmFetch a single alarm by its OCID, returning its MQL query, severity, destinations, and lifecycle state.
  • OCI Monitoring: Get Alarm HistoryRetrieve the history entries for an alarm: the record of state and rule changes (e.g. OK to Firing) over time. Optionally filter by entry type and an RFC3339 timestamp window. Walks pagination up to a safe cap.
  • OCI Monitoring: Get Alarm SuppressionFetch a single alarm suppression by its OCID, including the suppression window, target, level, and any recurrence preconditions.
  • OCI Monitoring: List Alarm StatusesList the current evaluation status (FIRING, OK or SUSPENDED) of the alarms in a compartment, optionally filtered to a single alarm by exact display name. Walks pagination up to a safe cap.
  • OCI Monitoring: List Alarm SuppressionsList the alarm suppressions in a compartment, optionally filtered to a single alarm by its OCID. Each suppression silences an alarm: whole or by dimension, for a time window. Walks pagination up to a safe cap.
  • OCI Monitoring: List AlarmsList the alarms in a compartment. Optionally filter by exact display name or lifecycle state (defaults to ACTIVE when unset). Walks pagination up to a safe cap.
  • OCI Monitoring: List MetricsList the metric definitions in a compartment. Filter by namespace, metric name (wildcards allowed, e.g. disk*), and dimension key/values. Returns definitions, not datapoints. Walks pagination up to a safe cap.
  • OCI Monitoring: Move Alarm to CompartmentMove an Oracle Cloud Monitoring alarm into a different compartment.
  • OCI Monitoring: Post Metric DataPublish a custom metric datapoint to a namespace with dimensions. Uses the telemetry-ingestion endpoint automatically. Timestamp defaults to now; supply an RFC3339 time to override.
  • OCI Monitoring: Summarize Metrics DataRetrieve aggregated metric data with an MQL query over a namespace. Returns one metric stream per dimension combination, each with timestamp/value datapoints. Time range defaults to the last 3 hours; supply RFC3339 start/end times to override.
  • OCI Monitoring: Update AlarmUpdate an existing alarm by OCID. Only the fields you fill in are changed: leave a field blank to keep its current value. Severity is CRITICAL/ERROR/WARNING/INFO; destinations are comma-separated Notifications topic OCIDs.

Also in Oracle Cloud

Put Monitoring in a flow

These actions sit on the same canvas as every other integration, so a Monitoring step can follow a form, a schedule or a message without any glue code.