View the Dashboard

You can view information about integration performance on the Integration dashboards page, including the error rate; the total number of instances, instances that succeeded, and instances in error; the number of active integrations; the status of connectivity agents; and design-time metrics.

You can view information about how your integrations are performing. The main page of the integration shows a snapshot of successful and failed integrations.

The Integration dashboards page reflects historical data. The number of all types of instance states (successful, failed, and so on) are collected hourly and displayed on the Integration dashboards page. Note the following details about the display of failed and recovered instances:

• Time 1: There are failed instances (shown in the Errors page)
• Time 2: The instances are then recovered (and are now successful)

If instance state information is collected between time 1 and 2, the Integration dashboards page shows some failed instances. The history graphs on the Integration dashboards page also show the hour/day during which that was the instance state. If the recovery of failed instances occurs before any new data is collected, the Integration dashboards page shows those instances as successful.

1. In the navigation pane, click Observability, then Dashboards.
   The Integration dashboards page is displayed by default. From the drop-down list, you can also select B2B to view the overall status of B2B transactions. See Monitor the Overall Health of B2B Transactions in Using B2B for Oracle Integration 3.
2. Click a section for dashboard details.
   
   

   
   Description of the illustration dashboards_page.png

   
   

   Section	Description	Actions
   Error rate (at least 24 hours) (This section is displayed by default.)	The instance status chart shows two bars per hour. The left bar shows the number of instances classified by their tracing level. This is important because the tracing level determines the life cycle of instances (for example, debug level tracing instances are purged in 24 hours) and the life cycle of the instance payload (for example, payloads captured for instances set to audit level tracing are purged in seven days). The right bar shows the number of instances classified by their states. The Incomplete state contains all instances that have not yet completed processing. These instances may be in the Queued, In Progress, Resubmitted, or Blocked states. Data outside the gray box (usually older historical data) does not retain or contain any information about instances set to debug level tracing. The following graphical and numerical information is also displayed: Error rate percentage; the number of failed, successful, terminated, and incomplete integration instances; and the total number of integration instances. Integration instances generated and processed at different tracing levels. Shows the number of emails sent per the enforced limit. The number includes successful and failed messages. See Monitor the Number of Emails Sent from Oracle Integration.	Select the time period for viewing integration instance status from the Instance Status list (24 hours (the default), the past week, the past month, or since the Oracle Integration instance was provisioned). The bar graphs and Overview section are refreshed to reflect information based on your selection. Click Track Instances to access the Instances page. See Track Integration Instances.
   Active integrations	Provides statistics on the number of scheduled, application, and event integrations, including the number in projects, packages, and standalone (globally available). The number of active integrations per Oracle Integration instance cannot exceed 800. Active integrations are defined as currently active integrations and integrations whose activations are in progress. If this number is: above 90% of the limit, a warning message is displayed. equal to or above the limit, a critical message is displayed.	Click Monitor integrations to access the Monitor integrations page. See Monitor the Message Processing Status of Integrations.
   Connections with errors	Displays a graph of connections with the most errors. The connection names appear to the right of the graph. The Overview section on the right shows the type of adapters with the most errors (for example, Oracle ERP Cloud Adapter, Salesforce Adapter, and others).	Click a section in the graph to access the Errors page, which lists the integration instances that use this connection. The connection name appears in the filtered search at the top of the Errors page. Click View more under Top connections with errors to go to the Errors page. The connection names and the total instance error counts for each are displayed with the Error by connection filter automatically selected. Error count totals are displayed in descending order.
   Unavailable agents	Displays the percentage of unavailable connectivity agents versus the number of currently running connectivity agents. The graph and Overview section provide statistics about the number of running and unavailable connectivity agents.	Click Monitor agents to access the Monitor Agents page. See Monitor Agents.
   Design time and audit	Displays a graphical view of the state of integration components. Active, configured, and draft integrations Active, configured, draft, and in-use connections In-use and configured lookups User-developed and recipe packages Connectivity agent groups Preinstalled adapters Configured and draft libraries By default, the Integrations section shows the number of integration patterns and adapters in use.	Hover over each chart to see the number of components in each state. Click the Integrations graph to show the integration patterns (application or schedule) and adapters in use. Click the Connections graph to show the number of each type of adapter in use. Click the Agents graph to show the agent groups in use. Click Audit to access the Design Time Audit page. See Check the Audit History for an Integration or Other Component.

Monitor the Number of Emails Sent from Oracle Integration

You can send up to 10,000 emails in a rolling 24-hour window from Oracle Integration. However, if you use your own customer tenancy, you can increase your limit to the number allowed by the Oracle Cloud Infrastructure Email Delivery Service. When your limit is exceeded, delivery occurs successfully one last time. For the next delivery, emails stop being sent and a Daily outbound email limit crossed error message is written to the activity stream for the impacted integration instance.

You monitor the current email count from the Email service section of the Integrations dashboard page. The count includes successful and failed messages. See View the Dashboard.

• How the Rolling 24 Hour Window is Calculated
• Increase the Limit on the Number of Emails to Send

How the Rolling 24 Hour Window is Calculated

• The email quota is built on a 24-hour rolling window. At any particular point in time, the last 24 hours of outbound emails are counted.
• When you exceed your quota in only one hour (same hour), you are blocked from sending emails for the next 24 hours.

To handle this type of scenario in your integration, you can also include the notification action in a scope action so that you can emit log messages in a fault handler and then resume instance processing, if required.

Increase the Limit on the Number of Emails to Send

The default method manages email delivery in Oracle Cloud Infrastructure. This tenancy limits the number of emails you can send in a rolling 24-hour window to 10,000 and the size of attachments to 2 MB.

If you instead use your own customer tenancy for sending emails, you receive the following benefits:

• The email limit is increased to the number allowed by the Oracle Cloud Infrastructure Email Delivery Service. The customer tenancy uses SMTP credentials to send email through the Oracle Cloud Infrastructure Email Delivery Service.
• You manage your approved senders and suppression list from your own customer tenancy instead of the Notifications page in Oracle Integration.

See Configure Notification Emails.

Check the Audit History for an Integration or Other Component

The Design Time Audit page shows the audit history of integrations and other components. Learn who updated a component, what changes they made, and when they made the update. This information is helpful for various scenarios, including troubleshooting unplanned changes.

1. In the navigation pane, click Observability, then Dashboards.
2. Click the Design time section.
3. Click Audit.
   The Design Time Audit page shows details about the audit for all invoked integrations.

   
   
   Description of the illustration oic3_audit_trail.png
   

4. Click Filter to filter data by time window, integration name, user name, or actions such as activate and deactivate.
5. Click Download, and select the following:
   • Download all: Downloads a maximum of 10,000 audit records.
   • Download filtered: Downloads records for the currently-selected filters.

   For example:

   [2022-06-18 00:57:56.372] [userId: l2gen3serviceadmin] [l2gen3serviceadmin,UNLOCK,ICS_ProjectV2,
   TEST_DEMO_FAULT_AGGR,TEST_DEMO_FAULT_AGGR,02.00.0000] User l2gen3serviceadmin unlocked Integration 
   TEST_DEMO_FAULT_AGGR 02.00.0000
   [2022-06-18 00:38:37.468] [userId: l2gen3serviceadmin] [l2gen3serviceadmin,LOCK,ICS_ProjectV2,TEST_DEMO_FAULT_AGGR,
   TEST_DEMO_FAULT_AGGR,02.00.0000] User l2gen3serviceadmin locked Integration TEST_DEMO_FAULT_AGGR 02.00.0000
   [2022-06-18 00:37:08.655] [userId: l2gen3serviceadmin] [l2gen3serviceadmin,UNLOCK,ICS_ProjectV2,PFE_SRS_FAUL_AGGR_G3_DD_MS,
   PFE_SRS_FAUL_AGGR_G3_DD_MS,02.00.0000] User l2gen3serviceadmin unlocked Integration PFE_SRS_FAUL_AGGR_G3_DD_MS 02.00.0000
   [2022-06-18 00:34:10.968] [userId: l2gen3serviceadmin] [l2gen3serviceadmin,LOCK,ICS_ProjectV2,PFE_SRS_FAUL_AGGR_G3_DD_MS,
   PFE_SRS_FAUL_AGGR_G3_DD_MS,02.00.0000] User l2gen3serviceadmin locked Integration PFE_SRS_FAUL_AGGR_G3_DD_MS 02.00.0000
   [2022-06-17 23:01:14.955] [userId: l2gen3serviceadmin] [l2gen3serviceadmin,UNLOCK,ICS_ProjectV2,PFE_SRS_FAUL_AGGR_G3_DD_MS,
   PFE_SRS_FAUL_AGGR_G3_DD_MS,02.00.0000] User l2gen3serviceadmin unlocked Integration PFE_SRS_FAUL_AGGR_G3_DD_MS 02.00.0000
   . . .
   . . .
   . . .

   The following table describes some of the actions that can appear.

   Action	Description	User Action
   activate	Indicates that the user activated an integration.	Activate the integration.
   activate_phase_change	Indicates that the user activated an integration. This action captures the intermediate state in the activation.	Activate the integration.
   audit_migration	Indicates that the user cloned an instance.	Clone the instance from the Settings page, under Import and Export.
   bulk_reactivation_completed	Indicates that the user performed a Save and Reactivate operation from the Connections page.	Save and reactivate the connection.
   bulk_reactivation_started	Indicates that the user performed a Save and Reactivate operation from the Connections page.	Save and reactivate the connection.
   clone	Indicates that the user cloned a resource (for example, integration, connection, or lookup).	Clone the resource.
   configure_integration	Indicates that the user configured an integration from the Configuration Editor page.	Configure the integration.
   create	Indicates that the user created a resource.	Create the resource.
   deactivate	Indicates that the user deactivated an integration.	Deactivate the integration.
   delete	Indicates that the user deleted a resource.	Delete the resource.
   delete certificate	Indicates that the user deleted the certificate.	Delete the certificate.
   import	Indicates that the user imported an integration or package.	Import the integration or package.
   instance_resubmission	Indicates that the user submitted a request to resubmit an errored instance for an integration.	Resubmit.
   instances_resubmission	Indicates that the user submitted a request to resubmit an errored instance for an integration.	Perform a bulk resubmit.
   instances_abort	Indicates that the user submitted a request to abort an errored instance for an integration.	Abort.
   instance_abort	Indicates that the user submitted a request to abort an errored instance for an integration.	Perform a bulk abort.
   instance_abort	Indicates that the user submitted a request to abort a running instance for an integration.	Abort.
   lock	Indicates that the user locked a resource.	Edit the resource.
   paused	Indicates that the user paused a schedule for an integration.	Pause the schedule.
   reactivation	Not being used.	- -
   reactivation_fail	Not being used.	- -
   register	Indicates that the user created an application type (that is, an adapter).	Create the adapter.
   resumed	Indicates that the user resumed a schedule for an integration.	Resume a schedule.
   started	Indicates that the user started a schedule for an integration.	Start a schedule.
   state_change	Indicates that the user activated an integration. This action captures the intermediate state in the activation.	Activate the integration.
   stop_schedule_deactivation	Not being used.	- -
   stopped	Indicates that the user stopped a schedule for an integration.	Stop the schedule.
   unlock	Indicates that the user unlocked a resource.	Edit and save a resource.
   update	Indicates that the user updated a resource.	Update the resource.
   update_schedule_parameter	Indicates that the user updated a schedule parameter's value for an integration.	Update the schedule parameter.
   upload_certificate	Indicates that the user uploaded the certificate.	Upload / create the certificate.

See the Current Status of All Integration Components

Get at-a-glance information about the number and status of your projects, integrations, connections, and more. For example, learn how many REST connections your organization has created.

This information can be helpful for showing your team's contributions, such as when you're compiling year-end metrics for the work that you've delivered.

1. In the navigation pane, click Observability, then Dashboards.
2. Along the top, select the Design time and audit box.

   The Design time metrics heading appears. A chart visualizes the components in your Oracle Integration instance.

3. Obtain metrics using one or both of the following options:

   • Below the Design time metrics heading, point to an entry in the chart, and view a metric in the tooltip that appears.

   • On the right, below the Integrations heading, obtain additional metrics.

     Tip:

     The table of metrics on the right often contains more information than can fit on the page. Point within the table of metrics to see a scroll bar, and scroll down to see additional metrics.
   
   

   

   
   

Check an Integration's Tracing Level

To ensure that your integrations are capturing the minimum required tracing information, consider routinely checking their tracing levels. For instance, Oracle recommends not using the Debug tracing level in production.

1. In the navigation pane, click Observability, then Dashboards.
2. Below the Instance status heading, select the appropriate time period to review from the drop-down.

   For instance, you might want to check the tracing levels for the last 24 hours or week.

3. Familiarize yourself with the chart that appears below Instance status.
   
   

   

   
   

   • Each time period contains two vertical bars.
   • The left bar visualizes the tracing levels for the integrations that ran during the time period.
   • The right bar visualizes the statuses for the integrations that ran during the time period.
4. Check the tracing levels for your integration instances for the time period.