- Support
- Integrations
- Monitoring
Monitoring
Oracle Cloud integration · 15 node(s).
00Overview
Watch your Oracle Cloud metrics and alarms straight from a flow — query metric data with the Monitoring Query Language, publish your own custom metrics, and create alarms that fire to a Notifications topic when a metric breaches a threshold. List and inspect alarms, check whether each one is firing, read an alarm's state history, and move alarms between compartments. You can also mute alarms with scheduled suppression windows for planned maintenance, all within one region and compartment you choose.
Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.
01Connecting Monitoring
- Recommended — Connect Oracle Cloud. In Flomation, open Environment settings and add an Oracle Cloud connection, give it a name, and complete the connection so it appears as a connected account you can pick. Flomation manages the signing key for you — there is no key to paste.
- In each Monitoring node, leave Authentication on Connect Oracle Cloud and pick your connection in the Oracle Cloud connection field — the tenancy, user, region and fingerprint are filled in for you. Set the node's Compartment OCID to the compartment you want to work in (use the tenancy OCID for the root).
- Advanced — API signing key. To use an existing key instead, set Authentication to API signing key (advanced) and fill Tenancy OCID, User OCID, Region (e.g.
uk-london-1) and Key Fingerprint from an API key on your OCI user (Identity → Users → API Keys). - For the advanced path, store the key's PEM as a Flomation environment secret (e.g.
monitoring_secret) and select it in the node's Private Key (PEM) field; add the Private Key Passphrase as a secret too, but only if the key is encrypted.
| Field | Type | Details | |
|---|---|---|---|
| Authentication | string | Connect Oracle Cloud, API signing key (advanced) | |
| Oracle Cloud connection | credential | Pick a connected Oracle Cloud account | |
| Region | string | e.g. uk-london-1 | |
| Private Key (PEM) | secret | The API signing private key — full PEM, incl. BEGIN/END lines | |
| Private Key Passphrase | secret | Only if the key is encrypted (optional) | |
| Tenancy OCID | string | ocid1.tenancy.oc1..aaaa… | |
| User OCID | string | ocid1.user.oc1..aaaa… | |
| Key Fingerprint | string | aa:bb:cc:… fingerprint of the uploaded API key |
Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.
02Alarm
OCI Monitoring: Move Alarm to Compartment
oracle/monitoring/alarm_change_compartment · Action
Move an Oracle Cloud Monitoring alarm into a different compartment.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | ocid1.compartment.oc1..aaaa… (the alarm's current compartment — scopes the alarm picker) | |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… of the alarm to move |
| Destination Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… to move the alarm into |
Returns: tool_result, id, destination_compartment_id, success, error
OCI Monitoring: Create Alarm
oracle/monitoring/alarm_create · Action
Create 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the alarm lives) |
| Display Name | string | Required | A name for the alarm |
| Metric Compartment OCID | string | Compartment whose metrics to watch (defaults to the alarm compartment) | |
| Metric Namespace | string | Required | e.g. oci_computeagent |
| MQL Query | text | Required | e.g. CpuUtilization[1m].mean() > 90 |
| Severity | string | Required | choices: Critical, Error, Warning, Info |
| Destinations (topic OCIDs) | string | Required | Comma-separated Notifications topic OCIDs |
| Pending Duration | string | ISO-8601, e.g. PT5M — breach must persist this long (optional) | |
| Resolution | string | e.g. 1m (optional) | |
| Notification Body | text | Message sent when the alarm fires (optional) | |
| Enabled | boolean | Enable the alarm now (default true) | |
| Freeform Tags (JSON) | string | {"env":"prod"} (optional) |
Returns: tool_result, alarm, id, lifecycle_state, success, error
OCI Monitoring: Delete Alarm
oracle/monitoring/alarm_delete · Action
Delete a Monitoring alarm by its OCID. This stops the alarm from evaluating and firing — it is permanent and synchronous.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the alarm lives) |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… (the alarm to delete) |
Returns: tool_result, id, success, error
OCI Monitoring: Get Alarm
oracle/monitoring/alarm_get · Action
Fetch a single alarm by its OCID, returning its MQL query, severity, destinations, and lifecycle state.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the alarm lives) |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… — the alarm to fetch |
Returns: tool_result, alarm, id, lifecycle_state, success, error
OCI Monitoring: Get Alarm History
oracle/monitoring/alarm_history_get · Action
Retrieve 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (not sent, but required by the credential block) |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… (the alarm to read history for) |
| History Type | string | Which entries to retrieve (default: all types) — choices: All types, State history, State transition history, Rule history, Rule transition history | |
| From Timestamp | string | RFC3339, e.g. 2026-07-01T00:00:00Z — entries on or after this (optional) | |
| To Timestamp | string | RFC3339, e.g. 2026-07-22T00:00:00Z — entries before this (optional) |
Returns: tool_result, entries, count, is_enabled, truncated, success, error
OCI Monitoring: List Alarms
oracle/monitoring/alarm_list · Action
List 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root) |
| Display Name Filter | string | Only alarms with this exact name (optional) | |
| Lifecycle State | string | Defaults to ACTIVE when unset — choices: Active, Deleting, Deleted |
Returns: tool_result, alarms, count, truncated, success, error
OCI Monitoring: Create Alarm Suppression
oracle/monitoring/alarm_suppression_create · Action
Mute 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the suppression lives) |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… (the alarm to suppress) |
| Display Name | string | Required | A name for the suppression |
| Suppress From | string | Required | RFC3339 start, e.g. 2026-07-22T01:00:00Z |
| Suppress Until | string | Required | RFC3339 end, e.g. 2026-07-22T03:00:00Z |
| Description | text | Reason for the suppression, e.g. Planned outage IT-1234 (optional) |
Returns: tool_result, alarm_suppression, id, success, error
OCI Monitoring: Delete Alarm Suppression
oracle/monitoring/alarm_suppression_delete · Action
Delete an alarm suppression by its OCID, lifting the silence it applied to the alarm. Synchronous — the suppression is removed immediately.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… |
| Alarm Suppression OCID | string | Required | ocid1.alarmsuppression.oc1..aaaa… (the suppression to delete) |
Returns: tool_result, id, success, error
OCI Monitoring: Get Alarm Suppression
oracle/monitoring/alarm_suppression_get · Action
Fetch a single alarm suppression by its OCID, including the suppression window, target, level, and any recurrence preconditions.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the suppression lives) |
| Alarm Suppression OCID | string | Required | ocid1.alarmsuppression.oc1..aaaa… |
Returns: tool_result, alarm_suppression, id, success, error
OCI Monitoring: List Alarm Suppressions
oracle/monitoring/alarm_suppression_list · Action
List 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root) |
| Alarm OCID Filter | string | Only suppressions targeting this alarm (optional) |
Returns: tool_result, alarm_suppressions, count, truncated, success, error
OCI Monitoring: Update Alarm
oracle/monitoring/alarm_update · Action
Update 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the alarm lives) |
| Alarm OCID | string | Required | ocid1.alarm.oc1..aaaa… (the alarm to update) |
| Display Name | string | New name for the alarm (leave blank to keep) | |
| Metric Namespace | string | e.g. oci_computeagent (leave blank to keep) | |
| MQL Query | text | e.g. CpuUtilization[1m].mean() > 90 (leave blank to keep) | |
| Severity | string | choices: (unchanged), Critical, Error, Warning, Info | |
| Destinations (topic OCIDs) | string | Comma-separated Notifications topic OCIDs (leave blank to keep) | |
| Pending Duration | string | ISO-8601, e.g. PT5M (leave blank to keep) | |
| Resolution | string | e.g. 1m (leave blank to keep) | |
| Notification Body | text | Message sent when the alarm fires (leave blank to keep) | |
| Enabled | boolean | Enable or disable the alarm (leave blank to keep) | |
| Freeform Tags (JSON) | string | {"env":"prod"} (leave blank to keep) |
Returns: tool_result, alarm, id, lifecycle_state, success, error
03Alarms
OCI Monitoring: List Alarm Statuses
oracle/monitoring/alarms_status_list · Action
List 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root) |
| Display Name Filter | string | Only the alarm with this exact display name (optional) | |
| Limit | string | Max results per page (optional) |
Returns: tool_result, alarm_statuses, count, truncated, success, error
04Metrics
OCI Monitoring: List Metrics
oracle/monitoring/metrics_list · Action
List 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root) |
| Namespace Filter | string | e.g. oci_computeagent (optional) | |
| Metric Name Filter | string | e.g. CpuUtilization or disk* (optional, wildcards allowed) | |
| Dimension Filters (JSON) | string | {"resourceId":"ocid1..."} (optional) |
Returns: tool_result, metrics, count, truncated, success, error
05Post
OCI Monitoring: Post Metric Data
oracle/monitoring/post_metric_data · Action
Publish 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (where the metric is posted) |
| Namespace | string | Required | e.g. my_app (custom namespace) |
| Metric Name | string | Required | e.g. orders_processed |
| Value | string | Required | The datapoint value, e.g. 42.5 |
| Dimensions (JSON) | string | Required | {"resourceId":"ocid1..."} — at least one required |
| Timestamp | string | RFC3339 (optional, defaults to now) | |
| Resource Group | string | Optional |
Returns: tool_result, failed_count, success, error
06Summarize
OCI Monitoring: Summarize Metrics Data
oracle/monitoring/summarize_metrics_data · Action
Retrieve 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.
| Field | Type | Details | |
|---|---|---|---|
| Compartment OCID | string | Required | ocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root) |
| Metric Namespace | string | Required | e.g. oci_computeagent |
| MQL Query | text | Required | e.g. CpuUtilization[1m].mean() |
| Start Time | string | RFC3339, e.g. 2026-07-22T09:00:00Z (optional, defaults to 3h ago) | |
| End Time | string | RFC3339, e.g. 2026-07-22T12:00:00Z (optional, defaults to now) | |
| Resolution | string | e.g. 5m — aggregation window frequency (optional, default 1m) |
Returns: tool_result, metric_data, count, success, error
07Notes & Limitations
Behaviours and constraints worth knowing before you build with these nodes.
- Each Oracle Cloud connection is tied to a single region, so monitoring resources across multiple regions requires a separate connection for each region.
- Alarm, metric, and status listings return results only from the compartment you specify and do not include resources in nested child compartments.
- Results from list, history, and status operations are capped at a fixed number of pages and marked as truncated when that limit is reached, so use the namespace, metric-name, and lifecycle-state filters to narrow large result sets.
- Alarm destinations are given as a comma-separated list of Notifications topic OCIDs, and those topics and their subscriptions must already exist before you create the alarm.
- Custom metrics you publish may take a short ingestion delay to become queryable.