View and analyze service instance metrics, including 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 message consumption is not included in Oracle Integration usage metrics.
Access the Metrics Page for an Oracle Integration Instance
🔗
Ensure you have permission to view message metrics for the compartment.
If you are an administrator with manage access, you can automatically
view message 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 toverb resource-typein compartmentcompartment-name
Policy:allow group oci-integration-admins to read metrics in compartment
OICPMCompartment
Shows the message requests that the instance received.
Successful messages
Shows the message requests that completed successfully.
Failed messages
Shows the message requests that did not complete successfully for the instance.
Inbound request processing time
Shows adapter inbound processing times for the instance.
Outbound request invocation time
Shows adapter outbound message invocation times for the instance.
Inbound requests
Shows the number of adapter inbound requests for the instance.
Outbound requests
Shows the number of adapter outbound requests for the instance.
Consumed messages
and
Configured messages
These two charts show the following information:
Consumed messages: Shows the number of messages that the instance used for incoming and outgoing messages for trigger and invoke requests.
Configured messages: Shows the number of messages that you purchased. This number is calculated by multiplying the number of message packs you purchased by the number of messages in each pack.
Use this data to make informed decisions about the number of message packs to purchase for the instance. See Choose a Message Pack Number.
Shows the number of messages used for extended data retention.
If you have an Enterprise edition instance and you choose to retain data longer than the default 32 days, an extra percentage will be added to your message consumption:
93 days (3 months) increases your message consumption by 10%.
184 days (6 months) increases your message consumption by 20%
Shows the number of messages that Visual Builder used.
3,500 messages for the first OCPU
4,500 messages for each additional OCPU
Consumed messages for process automation
Shows the number of process 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
Consumed messages for decisions
Shows the number of messages that decisions used.
+1 message per decision invocation
Consumed messages for robotic process automation
Shows the number of messages that Robotic Process Automation used.
+1 message per robot invocation
+1 message per 5 minutes of robot duration after the first 5 minutes
Total consumed messages
Shows the total number of messages used by all components and extended data retention.
Consumed message packs from overage
Shows the number of message packs used to cover any message usage overage.
Consumed message packs from breakglass
Shows the number of message packs that the instance used for breakglass.
Total consumed message packs
Shows the grand total of message packs used by your instance.
Using the Metrics Charts 🔗
You can change the metrics that appear in each chart. Additionally, you can create custom charts to further analyze your data. For example, imagine you created two compartments for your organization, one for your engineering team and another for your finance team. Using custom charts, you could measure the resources that each compartment used and determine whether you purchased an appropriate number of message packs.
Change the message metrics displayed for each chart, if needed.
Start Time and End Time are
selected at the top of each chart. Change these values to select a different time
period.
Metric counts occur every five minutes.
To change the metrics displayed, change the Interval
and Statistic fields for each chart.
To create custom dashboards and alerts, or to see data for all instances in a compartment, in the top right of a chart, from the Options drop-down list, select View Query in Metrics Explorer. For more information, see Viewing Default Metric Charts.
Options for Configuring the Charts 🔗
You can configure and view metrics charts that show adapter inbound request
processing times, outbound request invocation times, adapter inbound request numbers, and
adapter outbound request numbers.
Endpoint metrics include the following dimensions that are available for
selection in the Metrics Explorer.
Note
Each endpoint metric has its own dimensions. Not all dimensions are available on all
endpoint metrics.
adapterIdentifier: Show data in the chart for a single adapter (internal
name) that is used either as a trigger for receiving or as an invoke for sending the
request to the external system.
account_subscription: Show data in the chart for a specific account type,
such as a universal credit model (UCM) account, an Oracle Integration for Saas account,
or a government account.
flowCode: Show data in the chart for a specific integration in Oracle Integration.
flowVersion: Show data in the chart for a specific integration version,
which you can specify at various times, including when you create or clone an
integration.
inboundProcessingEndpointInformation: Show data in the chart for a specific
functional request received from the client.
inboundProcessingResponseStatus: Show data in the chart for a specific
status sent by the trigger to the external client.
instanceName: Show data in the chart for a specific instance. This value
matches the name that an administrator specified when creating the instance as well as the
URL of the instance. This value is a more user-friendly value than the resourceid.
meterType: Show data in the chart for a specific license type, such as BYOL,
Cloud, or SaaS.
outboundInvocationEndpointInformation: Show data in the chart for a
specific functional request made to the external system.
outboundInvocationResponseStatus: Show data in the chart for a specific
status received from the external system.
integrationFlowIdentifier: Show data in the chart for the integration
receiving an incoming request or sending an outgoing request. The dimension includes both
the identifier and the version.
resourceid: Show data in the chart for a specific OCID of an integration
instance. You can use this value to uniquely track the instance.
Tip:
To filter a chart by
multiple metric dimensions, first select a dimension name and dimension value. Then, click
Additional dimension and select another dimension name and value.
Don't forget to click Update Chart after updating the query.
The metrics listed in the following tables are automatically available for
selection for any instance you create.
The inboundProcessingEndpointInformation or
outboundInvocationEndpointInformation dimension provides a concise summary of the adapter
trigger or invoke configurations. For example, the inboundProcessingEndpointInformation
dimension can look for ‘Receive Incident Created notification from ServiceNow’ for an
integration that is triggered when an incident is created in the ServiceNow application. On
the invoke side, the outboundInvocationEndpointInformation dimension can look for ‘Create
Account in Salesforce.com’ if the invoke activity in the integration is configured to create
an Account object in Salesforce.com.
The following table describes the available metrics and dimensions. The
Commonly Used Statistics in Metrics Explorer column provides the following information.
Mean: Average processing time (latency) taken for incoming requests
received during the time interval and average invocation time taken by outbound requests
sent during the time interval.
Min: Minimum processing time (latency) taken for incoming requests received
during the time interval and minimum invocation time taken by outbound requests sent
during the time interval.
Max: Maximum invocation time taken by outbound requests sent during the time
interval and maximum processing time (latency) taken for incoming requests received during
the time interval.
P50: Maximum invocation time (latency) taken by 50% of outbound requests
sent during the time interval and maximum processing time (latency) taken by 50% of
incoming requests received during the time interval.
P90: Maximum invocation time (latency) taken by 90% of outbound requests
sent during the time interval and maximum processing time (latency) taken by 90% of
incoming requests received during the time interval.
P95: Maximum invocation time (latency) taken by 95% of outbound requests
sent during the time interval and maximum processing time (latency) taken by 95% of
incoming requests received during the time interval.
P99: Maximum invocation time (latency) taken by 99% of outbound requests
sent during the time interval and maximum processing time (latency) taken by 99% of
incoming requests received during the time interval.
Count: Total number of requests received during the time interval and total number of
outbound requests made during the time interval.
Endpoint Metrics 🔗
Metric Name in Metrics Explorer
Unit
Description
Dimension Name in Metrics Explorer
Commonly Used Statistics in Metrics Explorer
ConfiguredMessages
count
Number of messages that were configured. This number determines billing.
account_subscription
instanceName
meterType
resourceId
Max
InboundRequestProcessingTime
Duration in milliseconds
The time taken for processing inbound requests. In case of
synchronous requests, it is the total time taken for processing a request and
sending the response. In case of fire-and-forget inbound requests, it is the time
taken to persist the request and send the acknowledgment.
This metric captures the time elapsed (in milliseconds) by the
trigger in processing the incoming request.
adapterIdentifier
inboundProcessingEndpointInformation
inboundProcessingResponseStatus
integrationFlowIdentifier
resourceid
Mean
Min
Max
P95
P99
MessagesFailedCount
count
Number of messages that could not be processed. For example, a
message can't be processed when an external endpoint that is used in an
integration goes down.
flowCode
flowVersion
resourceId
Max
MessagesReceivedCount
count
Number of messages that were received. This count doesn't indicate
whether the messages processed successfully.
flowCode
flowVersion
resourceId
Min
Max
MessagesSuccessfulCount
count
Number of messages that were processed successfully.
flowCode
flowVersion
resourceId
Min
Max
NumberofInboundRequests
count
Number of requests received by Oracle Integration using any adapter-specific
trigger connection. This metric includes the HTTPs requests posted to Oracle Integration and the messages polled by adapters such as Oracle Advanced Queuing (AQ)
Adapter, IBM MQ Series JMS
Adapter, Apache Kafka Adapter, Oracle Database Adapter, and so on.
adapterIdentifier
inboundProcessingEndpointInformation
inboundProcessingResponseStatus
integrationFlowIdentifier
resourceid
Count
NumberOfOutboundRequests
count
Number of outbound requests sent by the adapter as part of the
invoke activity in Oracle Integration.
adapterIdentifier
integrationFlowIdentifier
outboundProcessingEndpointInformation
outboundProcessingResponseStatus
resourceid
Count
OutboundRequestInvocationTime
Duration in milliseconds
Time (in milliseconds) spent by the adapter during the invocation of the target
endpoint.
adapterIdentifier
integrationFlowIdentifier
outboundProcessingEndpointInformation
outboundProcessingResponseStatus
resourceid
Mean
Min
Max
P50
P90
P95
P99
How Adapters Map to Dimension Values 🔗
The following table describes how each adapter maps to its dimension value in
the Metrics Explorer.
Dimension Value in Metrics Explorer
Adapter Display Name
Inbound Processing Event Information Naming Conventions in
Dimension Value Field
Outbound Invocation Endpoint Information Naming Conventions in
Dimension Value Field
adobeesign
Adobe Sign Adapter
N/A
Retrieve status of agreement from Adobe eSign
Upload a document in Adobe eSign
Retrieve IDs of agreement from Adobe eSign
Retrieve URL of the document from Adobe eSign
adwdatabase
Oracle Autonomous Data Warehouse
Adapter
New row is inserted into <table name> in Oracle ADW
Insert rows into <table name> in Oracle ADW
Merge rows into < table name> in Oracle ADW
Update rows into <table name> in Oracle ADW
apachekafka
Apache Kafka Adapter
Consume latest message from Topic:
[TopicName=<Topic>,Partitions={<Partition>}] in Apache Kafka
Produce message(JSON) in Topic:
[TopicName=<Topic>,Partitions={<Partition>}] using Apache Kafka
Consume latest message from Topic:
[TopicName=<Topic>,Partitions={<Partition>}] in Apache Kafka
aq
Oracle Advanced Queuing (AQ)
Adapter
Consume <message type> message from Queue: <queue
name> in Oracle Advanced Queueing (AQ)
Produce <message type> message in Queue: <queue name>
using Oracle Advanced Queuing (AQ)
ariba
SAP Ariba Adapter
Receive notification from <operation name> from Ariba
Create <business object> in SAP Ariba
Bulk upload for the task - <task name> <Data Mode:
Master/Transactional, Operation Mode: Incremental/Full> in SAP Ariba
Bulk extract for the task - <task name> <Data Mode:
Master/Transactional, Operation Mode: Incremental/Full> from SAP Ariba
as2adapter
AS2 Adapter
N/A
N/A
atpdatabase
Oracle Autonomous Transaction Processing
Adapter
New row is inserted into <table name> in Oracle ATP
insert rows into <table name> in Oracle ATP
Merge rows into < table name> in Oracle ATP
Update rows into <table name> in Oracle ATP
bbtranslationadapter
EDI Translate Action
N/A
B2B EDI Translation
box
Box Adapter
N/A
N/A
concur
SAP Concur Adapter
NA
Create/Update/Delete/Retrieve <business object> in SAP
Concur.
Extracts reports of available data objects in SAP Concur.
Manage payment batches and retrieve their batch files in SAP
Concur.
Get status for the Job in Concur
Download file from Concur application
Bulk data extract request for AP/GL Extract V.3.04 submitted in
Concur
cpq
Oracle CPQ Adapter
N/A
N/A
database
Oracle Database Adapter
New row is inserted into <table name> in Oracle
Database
Insert rows into <table name> in Oracle Database
Merge rows into < table name> in Oracle Database
Update rows into <table name> in Oracle Database
dbaasdatabase
Oracle Database Cloud Service
Adapter
New row is inserted into <table name> in DBCS
Insert rows into <table name> in DBCS
Merge rows into < table name> in DBCS
Update rows into <table name> in DBCS
db2database
IBM DB2 Adapter
New row is inserted into <table name> in DB2
Insert rows into <table name> in DB2
Merge rows into < table name> in DB2
Update rows into <table name> in DB2
docusign
DocuSign Adapter
N/A
Create and send an envelope in DocuSign
Send an envelope created from an existing template in
DocuSign
GET : Get specific item from the collection<Entity_NAME>
from SAP S/4HANA
GET : GetAll entities in the collections of <Entity_NAME>
from SAP S/4HANA
POST : Create new item in the collection <Entity_NAME> from
SAP S/4HANA
PATCH : Update new item in the collection <Entity_NAME> from
SAP S/4HANA
DELETE : Delete specific entity in the collection from SAP S/4HANA
servicenow
ServiceNow Adapter
Receive <business object> notifications from
ServiceNow
For Query : <operation>from ServiceNow
For Create/Update/Delete:<operation> in ServiceNow
Upload Attachment to ServiceNow
shopify
Shopify Adapter
Receive <business object event> from Shopify
For Query : <<operationName>> from Shopify
For Create/Update/Delete:<<operationName>> in
Shopify
siebel
Oracle Siebel Adapter
N/A
Call Siebel SOAP Service OS FS Get Stock Oracle Integration
<Service>:<Operation>
slack
Slack Adapter
N/A
N/A
SOAAdapter
Oracle SOA Suite Adapter (includes Oracle Service Bus and Oracle SOA Cloud Service)
N.A.
Call a << REST / SOAP >> service on a << SOA
Composite / Service Bus project >>
soap
SOAP Adapter
Trigger Oracle Integration SOAP Integration for the interface
<Port Type> : <operation name>
Call External SOAP API <Port Type> :
<operation-name>
sqlserverdatabase
Microsoft SQL Server
Adapter
New row is inserted into <table name> in MS SQL Server
DB
Insert rows into <table name> in MS SQL Server DB
Merge rows into < table name> in MS SQL Server DB
Update rows into <table name> in MS SQL Server DB
Successfactors
SAP SuccessFactors
Adapter
Receive <<operationName>>
<<BusinessObject>> from SuccessFactors
Query data from SuccessFactors using SFQL query
Create <<BusinessObject>> in SuccessFactors
Update <<BusinessObject>>in SuccessFactors
Delete <<BusinessObject>>in SuccessFactors
Create or update <<BusinessObject>> in
SuccessFactors
sugarcrm
SugarCRM Adapter
N/A
For Query(Retrive single/list of Records) : <operation>from
SugarCRM
For Create/Update/Delete:<operation> in SugarCRM
surveymonkey
SurveyMonkey
Adapter
N/A
N/A
otac
Oracle Taleo Enterprise Edition
Adapter
N/A
Get request status from Oracle Talent Acquisition Cloud (Taleo
EE)
Get request status from Oracle Talent Acquisition Cloud (Taleo
EE)
trello
Trello Adapter
N/A
N/A
twilio
Twilio Adapter
N/A
N/A
twitter
Twitter Adapter
N/A
N/A
workday
Workday Adapter
N/A
Create, Update, Delete, and Import records in Workday
Extract bulk data from workday
zendesk
Zendesk Adapter
N/A
Get Single Record: Get <Entity_NAME> from Zendesk
Get List of Records: Get <Entity_NAME>s from Zendesk
Create a Record: Create <Entity_NAME> in Zendesk
Update a Record: Update <Entity_NAME> in Zendesk
Update multiple Records: Update <Entity_NAME>s in Zendesk
Update multiple Records in batches: Update <Entity_NAME>s in
batches in Zendesk
Search multiple Records: Search <Entity_NAME>s in Zendesk
Delete a Record: Delete <Entity_NAME> from Zendesk
Create or Update a Record: Create or Update <Entity_NAME> in
Zendesk
Upload an Attachment: Upload Attachment in Zendesk
Redact Attachment: Redact Comment Attachment in Zendesk
Example of an Endpoint Metric Chart 🔗
The following example of an endpoint metrics chart is provided. The chart shows
adapter inbound request processing times. A metrics namespace is provided that is a
container for message metrics. The namespace identifies the service sending the metrics. The
namespace for message metrics is oci_integration. Description of the illustration processing_time.png
Adapters with Limited Dimensions 🔗
The following adapters do not publish inboundProcessingEndpointInformation and
outboundInvocationEndpointInformation dimensions in the Metrics Explorer.