Monitor Integrations

Use the Oracle Integration dashboard to see how your integrations are performing. The dashboard provides multiple views for you to check your running services.

View the Dashboard

You can view information about how your integrations are performing on the Dashboard page. The Dashboard data represents the entire history of the instance, including the number of messages before purging, if it ever occurred.

You can view information about how your integrations are performing. The main page of the integration shows a snapshot of a state of all running integrations.
To view the dashboard:
  1. In the navigation pane, click Home > Monitoring > Integrations > Dashboard.

    The Dashboard page provides the following details:

    • Success rate for messages (the number of messages received and the number of messages with errors since the Oracle Integration instance was provisioned).

    • System health, including the service instance status, agent status, number of emails sent and total number of emails available to send, and number of active integrations. The number of active integrations per Oracle Integration instance cannot exceed 700. 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
    • Agent health (the total number of agents versus the number of agents currently not running).
    • Number of active integrations and how they were triggered (for example, by schedules or by events).

      Click More to access the Monitor Integrations page. See Monitor Integrations.

    • Number of scheduled integrations (running and currently paused).
    • Design-time metrics showing the number of connections, integrations, adapters, and schedules. Click More to access the Design-Time Metrics page. See View the Design-Time Metrics.
    • Graphs showing the hourly and daily history of total, successful, and failed instances. You can place your cursor over the bars in each graph to display the total number of successful messages and failed instances.

    The Dashboard page reflects historical data. The number of all types of instance states (successful, failed, and so on) are collected hourly and displayed on the Dashboard 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 Dashboard page shows some failed instances. The history graphs on the Dashboard 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 Dashboard page shows those instances as successful.


  2. From the View menu, select an option:
  3. From the Logs menu, select the type of log to download. This menu is not available if you are using Oracle Integration Generation 2.
    • Diagnostic Logs: If you are having problems with an integration, you can attach the diagnostic logs to a service request for help in debugging the issue.
    • Incident Logs: Click to download the created incident report. See Report Incidents.

      Note:

      The ability to download incident logs has been deprecated.

View the Activity Stream from the Dashboard Page

You can view the activity stream and message activity of invoked integrations. The activity stream provides status about the payload as it moves through the integration during runtime, including any failures.

Note:

  • During periods of high loads, expect a delay in the display of instance activity data. This is because the data in the log file may not be available. The logging action in orchestrated integrations may take some time to write the data into the log file. The amount of time it takes to write the data to the log file is based on the size of the load.

  • After activation of an integration, there is a several second delay between when the first instance is created and when the message is processed in the activity stream. This is the expected behavior. See Delay in Message Processing of First Instance after Activation.
  • The supported total size of the activity stream is restricted to less than 100 MB.

    The maximum size for payloads inside the activity stream is 512 KB, at which time the payloads are truncated.

    See Activity Stream Logs Deleted.

To view the activity stream from the Dashboard page:

  1. From the View menu, select Activity Stream. The Activity Stream page shows details about the activity stream of invoked integrations.
  2. Click Download to download the activity stream.

View the Design-Time Audit

You can view the design-time audit of all integrations.

To view the design-time audit:
  1. From the View menu, select Design Time Audit.
    The Design Time Audit page shows details about the audit for all invoked integrations.

  2. Click Download to download the design-time audit.

View the Design-Time Metrics

You can view the design-time metrics of Oracle Integration, including details about integrations, connections, lookups, packages, agents, and adapters.

To view the design-time metrics of Oracle Integration:
  1. In the navigation pane, click Home > Monitoring > Integrations > Dashboard.
  2. In the Design Time Metrics box, view the number of connections, integrations, adapters, and schedules.
  3. Click the More link.
  4. View details about the following components in Oracle Integration:
    • The state of integrations (draft (under construction), configured, active, and failed).

    • The state of connections (draft, configured, in use, and active).

    • The number of lookups, including in use.

    • The number of packages (developed and prebuilt).

    • The number of connectivity agents.

    • The number of adapters (preinstalled, private, and marketplace).

    • The number of libraries (draft and configured).



  5. Click the > arrow for Integrations to display details about the number of integrations configured for the following:
    • Application-driven integrations

    • Basic routing integrations

    • Publish to OIC

    • Subscribe to OIC

    • Scheduled orchestrations

  6. Click the > arrow for Integrations again to view how many integrations are using each adapter.
  7. Click the > arrows for Connections and Agents to view more specific details about the configured adapters and configured agents (execution and connectivity).

Monitor the Number of Emails Sent from Oracle Integration

You can send up to 10,000 emails daily from Oracle Integration. When the limit is exceeded, email delivery occurs successfully one last time. For the next (second) 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 can monitor the current email count on the Dashboard.

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 execution, if required.

Note the following:
  • 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.
  1. Invoke integrations that use the notification action.
  2. In the navigation pane, click Home > Monitoring > Integrations > Dashboard.
  3. Monitor message delivery quota status from the System Health section of the Dashboard page. For this example, the daily quota is set to 10000 (the default value) and 0 messages have been sent (quota not yet exceeded).
  4. Continue to invoke integrations. For this example, a REST Adapter trigger-based integration is invoked from the Test page. See Test REST Adapter Trigger Connection-Based Integrations.
  5. View the activity stream for the integration instances. When the email quota is exceeded for a second time, an error message is displayed in the activity stream. For example:This image shows the Test UI on the left. On the right is the activity stream for the invoked integration. The instance ID value appears at the top. To the right is the Ascending option. Below this is the Iteration section, which shows the status of actions in the integration flow. An error is displayed for the notification action: Sending email notification failed due to:Daily outbound email limit crossed.

Monitor Integrations

The Monitor Integrations page enables you to view the message processing status of your running integrations, such as how many messages have been received and processed, how many successful messages and errors have occurred, and how many messages have been aborted. Only activated integrations are listed on this page by default. Using the appropriate filter, you can also view data for inactive integrations.

A Total Instance Count summary is displayed at the top of the page. This section is collapsed by default. Data is not immediately fetched. To fetch and view data, expand the Total Instance Count section and click the Refresh button visible within the section.

This summary shows the count of total available messages in various states present in the tracking store. This summary is different from the metrics shown on the Dashboard page. While the Dashboard page metrics consist of historical data collected since the environment was created, the Monitor Integrations page shows only the current set of messages that have not yet been purged.

To monitor integrations:

  1. In the navigation pane, click Home > Monitoring > Integrations > Integrations.
    A list of active integrations appears by default, along with processing information about the number of messages received, the number of messages processed, the number of successful messages, the number of failed messages, and the number of aborted messages. For scheduled integrations, navigation links are provided that take you to the Schedule and Future Runs page.
  2. From the Filter icon link, select the time window, integration status, or integration style for which to search for integrations.
    You can also specify a custom time range by clicking Filter icon to filter the search for integrations with the From and To buttons at the bottom. This functionality also exists on other monitoring pages such as the Track Instances or Errors page. See Step 3 of Track Business Identifiers in Integrations During Runtime for details.


    The user who last submitted the schedule of an integration is displayed in the Last Scheduled By column. For non-scheduled integrations such as app driven integrations or basic routing integrations, this column remains empty.

    The values shown in the table columns are based on the selected time window (last 1 hour, last 6 hours, and so on):
    • Received: Shows the number of new incoming messages (or instances created). It is possible that some of these messages will not complete processing within the selected time window.
    • Processed: Shows the sum of the Succeeded, Errored. and Aborted column values. This is the number of messages that completed processing in the selected time window. Some messages may have been received in a prior time window, but completed processing during the currently-selected window.
    • Succeeded, Errored, and Aborted: The explanation is the same as the Processed column count. The only difference is the different terminal states.

    A difference can exist between the number of messages listed in the Received and Processed columns. For example, assume there are 76 Received column messages and 184 Processed column messages. This means that for the selected time window, 76 new messages were received. In that same time window, 184 messages completed processing. Many of the 184 would have been received before the selected time window, and therefore not counted in the Received message total. Similarly, many of the 76 Received messages may not complete within the selected time window. Therefore, even though they are counted in the Received total, they are not counted in the Processed total.

  3. Click numbers in the Received, Processed, Succeeded, and Aborted columns to access the Track Instances page.
  4. Click numbers in the Errored column to access the Errors page.
  5. For scheduled integrations (identified by Scheduled integration icon), you can perform the following tasks:
    1. Click Submit Now button to submit the integration now. If you are a user with the ServiceAdministrator role, you can change the user with which to submit the schedule.
    2. Click Actions menu to schedule an integration or pause a schedule.

Monitor Agents

You can monitor the agent groups and their associated connectivity agents in Oracle Integration.

To monitor a connectivity agent:

  1. In the left navigation pane, click Home > Monitoring > Integrations > Agents.



  2. The Agent Monitoring page shows details such as the time at which the agents were last updated and the connectivity agents associated with the agent groups.

    • If the agent status is green, this indicates that the agent is running and able to process messages.

    • If the agent status is red, you cannot select it in the Select an Agent Group dialog of the Connections page, even though the agent may be up and running. Review the agent-diagnostic0.log file under agenthome/logs for more detailed information about errors.

  3. Expand the agent group name to see the connectivity agent associated with this group.

  4. Click Open Details icon to also show details about the agent group such as creation date and the last startup date of the connectivity agent.

Note:

When you shut down the agent server, several minutes pass before the agent is displayed as down on the Agent Monitoring page (as indicated by a red thunderbolt).