Oracle Cloud Infrastructure Documentation

View Service Instance and Billing Message Metrics

View and analyze service instance metrics, including billing message data, processing and invocation times, adapter requests, and configured and consumed messages on the Metrics page. Use the data to monitor resources associated with Oracle Integration and the applications that you integrate with Oracle Integration.

Note

Visual Builder billing message consumption is not included in Oracle Integration usage metrics.

View the Default Metrics for an Oracle Integration Instance

Prerequisite:

Ensure you have permission to view service instance metrics for the compartment.
  • If you are an administrator with manage access, you can automatically view service instance metrics for the compartment. For manage access, you must be part of an Oracle Cloud Infrastructure group assigned a manage policy.
  • If you are an administrator with read only access, you must be part of an Oracle Cloud Infrastructure group assigned a read metrics policy.
For example:
  • Syntax: allow group group_name to verb resource-type in compartment compartment-name
  • Policy: allow group oci-integration-admins to read metrics in compartment OICPMCompartment

See Manage Access and Assign Roles.

To view the metrics:

  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Open the navigation menu and click Developer Services. Under Application Integration, click Integration.
  3. Click an Oracle Integration instance to view it.

    Scroll down to the Metrics section, which shows charts with default values.


    Description of oci_monitoring_metrics.png follows
    Description of the illustration oci_monitoring_metrics.png

For information on using the charts, including descriptions of the Statistic options, see Viewing Default Metric Charts in the Oracle Cloud Infrastructure documentation.

Available Metrics Charts

Note

Billing for Oracle Integration is changing on July 1, 2025. Starting then, using the following features will result in extra billing message usage:
  • Disaster recovery
  • Robotic process automation
  • Extended data retention

These updates are included in our Service Description, which is part of your agreement with Oracle.

Review the metrics in these charts to determine how these features contribute to your total usage. If you use any of these features after July 1, 2025, your bill may increase. If you don't want to continue use of these features, disable them before July 1, 2025 to avoid extra billing message usage.

Chart Description
Received messages Shows the number message requests that the service instance received.
Successful messages Shows the number message requests that completed successfully.
Failed messages Shows the number message requests that did not complete successfully.
Inbound request processing time Shows the amount of time taken to process inbound requests.
Outbound request invocation time Shows the amount of time taken to invoke outbound requests to external endpoints.
Inbound requests Shows the number of inbound requests received by the service instance.
Outbound requests Shows the number of outbound requests made by the service instance.
Consumed messages Shows the number of billing messages that the service instance used for incoming and outgoing messages for trigger and invoke requests.

For details on how billing message usage is calculated, see Estimate Billing Message Usage for a Metered Tenancy.

Configured messages Shows the number of billing messages that you purchased. This number is calculated by multiplying the number of message packs you purchased by the number of billing messages in each pack.

For information on the number of billing messages in each pack and how to select the number of message packs, see Choose a Message Pack Number.

Consumed messages from data retention Shows the number of billing messages used for extended data retention.

By default Standard and Enterprise edition service instances retain data for 32 days, and Healthcare edition service instances retain data for 184 days. If you have an Enterprise edition service instance, you can change the data retention period if you want.

Adding extended data retention increases your hourly billing message consumption:

  • 93 days (3 months) increases your billing message consumption by 10% ("Consumed billing messages" x 10%)
  • 184 days (6 months) increases your billing message consumption by 20% ("Consumed billing messages" x 20%)

For details on how data retention billing message usage is calculated, see Extended Data Retention Message Consumption.

For details on how to manage your data retention period, see Edit the Data Retention Period for an Instance.

Consumed messages for process automation Shows the number of process billing messages that Process Automation used.
  • +1 message per process invocation

    A process invoking another process doesn't incur this charge

  • +1 message per hour of process duration after the first hour

For details on how Process Automation billing message usage is calculated, see Additional Message Consumption for Optional Features.

Consumed messages for decisions Shows the number of billing messages that decisions used.

Based on your existing message pack consumption, which includes additional billing message consumption due to other services, limits, components, and overages.

  • +1 message per decision invocation

For details on how decision billing message usage is calculated, see Additional Message Consumption for Optional Features.

Consumed messages for robotic process automation Shows the number of billing messages that robotic process automation used.
  • +1 message per robot invocation
  • +1 message per 5 minutes of robot duration after the first 5 minutes

For details on how robotic process automation billing message usage is calculated, see Additional Message Consumption for Optional Features.

Consumed message packs for disaster recovery Shows the number of message packs used for disaster recovery.

Adding disaster recovery increases your message pack consumption based on your existing message pack consumption. Existing message pack consumption is the number of message packs consumed by integrations, data retention, Process Automation, decisions, and robotic process automation.

  • If your existing message pack consumption is 1-3 message packs, disaster recovery adds 1 message pack.
  • If your existing message pack consumption is 4-8 message packs, disaster recovery adds 2 message pack.
  • If your existing message pack consumption is 8+ message packs, disaster recovery adds 3 message pack.

For details on how disaster recovery message pack usage is calculated, see Disaster Recovery Message Consumption.

Total consumed messages Shows the total number of billing messages used by all components except Visual Builder. This total doesn't include disaster recovery.

For details on how total consumed billing message usage is calculated, see Estimate Billing Message Usage for a Metered Tenancy.

Total consumed message packs Shows the grand total of message packs used by your service instance, including the message packs to cover your total consumed billing messages, plus the message packs used for disaster recovery.

For details on how the total is calculated, see Estimate Billing Message Usage for a Metered Tenancy.