Find Integrations That Experienced Errors

When you're responsible for monitoring integrations, part of your job involves determining whether any integrations experienced errors and then taking the appropriate next steps.

Errors in live integrations are never expected. Oracle recommends investigating every error that an integration experiences.

Find Integrations with Errors

Oracle recommends investigating every error that occurs with your integrations.

  1. In the navigation pane, click Observability, then Integrations.
  2. Click Filter Filter icon, and update the filtering requirements for the page.
  3. In the Errored column, look for any non-zero values.

Determine the Source of an Integration's Error

Find the source of an error by checking the activity stream. You can also see the location of the error within an integration flow on the integration canvas.

  1. In the navigation pane, click Observability, then Integrations.
  2. Click Filter Filter icon, and update the filtering requirements for the page.
  3. In the Errored column, look for any non-zero values.
  4. For an integration with one or more errors, determine the location of the error(s).
    1. Click the number value in the Errored column for the integration.
      The Errors page appears and shows only the integration instances that experienced errors.
    2. For an error, review the value in the Fault location column.
      The fault location indicates where the error occurred. For example, if errors occurred for an invoke that multiple integration instances use, the application that the invoke connection is connecting to might be unavailable.
  5. Locate the source of the issue by reviewing the activity stream.
    1. Hover over an errored integration instance, and select View details View icon.
      The activity stream opens.
    2. In the activity stream, find the milestone with an error and open the activity stream from it using one of the following options.
      • If View payload View iconappears on the milestone, click View payload View icon.
        A milestone with an error appears in the activity stream

      • If View payload View icon doesn't appear on the milestone, expand the milestone by clicking the expand icon >, and then click View payload View icon for the part of the integration flow that failed.
        A mouse cursor hovers over the > icon in a milestone that appears in the activity stream

    3. Review the payload and take the appropriate action.
      For example, if a 404 error occurred, check the configuration of the connection.
  6. Optional: To see the error within the integration flow, open the integration canvas.
    1. On the Errors page, in the Primary identifier column, click the name of the primary identifier, such as Primary: undefined.

      The integration canvas appears. The integration component with an error is marked in red.
      An integration component is outlined in red, indicating that an error occurred for the componenet

    2. To see the error in the activity stream: Point to the component with an error, click Actions Actions icon, and select Activity stream.

      The activity stream opens.

  7. If you are not responsible for addressing the error, send the error information to the owner of the integration.
    For example, you might perform some or all of the following steps:
    • Take a screenshot of the activity stream.
    • Copy the payload text.
    • Download the logs for the activity stream.

      Tip:

      Click Download Logs Download icon at the top of the activity stream.

Find the Integration Error Rate for the Last 24 Hours

Consider completing a daily check of your integration error rate over the last 24 hours. If the value is greater than 0, investigate the errors.

  1. In the navigation pane, click Observability, then Dashboards.
  2. Along the top of the page, make sure that Error rate (past 24 hours) is selected.
  3. Review the value in the Error rate (past 24 hours) box.

    This metric shows the percentage of integration instances that experienced errors in the last 24 hours.

Measure Your Integration Errors Over Time

Measuring your integration errors over time can help you track trends and measuring improvements.

  1. In the navigation pane, click Observability, then Dashboards.
  2. Below the Instance status header, use the drop-down to adjust the time period, if necessary.
  3. Review a chart to visually track your errored integrations over time.
    1. Familiarize yourself with the chart that appears below Instance status.

      The bar chart shows 7 days of information, with varying measurements for each day.

      • 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.
    2. Determine whether any integration instances experienced errors during the time period.
  4. Review the metrics to understand how many integration instances have experienced errors over time.

    The error-related metrics appear to the right of the chart, below the Overview heading.

    • Error rate: Error rate for all of the integration instances during the time period.
    • Instances: Number of integration instances that ran during the time period.
    • Errors: Number of integration instances with a state of Errored during the time period.

Find the Connections with the Most Errors

Knowing the connections that result in integration instances with errors can help you quickly prioritize integration failures and start the troubleshooting process.

Why Connections Experience Errors

The typical causes of connection errors are varied and depend upon the adapters you use, the way you use the connections, and your use cases. For example:

  • The integration developer configured the connection incorrectly.

    In this case, the connection always fails.

  • The connection cannot complete its task.

    Consider a connection that is based on the FTP Adapter. The connection fails if someone moves or deletes the folder that the integration reads from or changes the permissions on the folder.

To Find the Connections with the Most Errors:

  1. In the navigation pane, click Observability, then Dashboards.
  2. Along the top, select the Connections with errors metric.

    The Top connections with errors section appears, listing up to five of the connections with the most errors.

  3. Below the Top connections with errors heading, point to the box for a connection.

    A tooltip displays the number of integration instances that use the connection and experienced an error.

  4. Find the integration instances that used the connection and experienced errors.
    1. Click within one of the connections boxes.

      The Errors page appears and shows only the integration instances that used the connection and experienced an error.

    2. Hover over an errored integration instance, and select View details View icon.

      The activity stream opens.

    3. In the activity stream, find the milestone with an error and open the activity stream from it using one of the following options.
      • If View payload View iconappears on the milestone, click View payload View icon.
        A milestone with an error appears in the activity stream

      • If View payload View icon doesn't appear on the milestone, expand the milestone by clicking the expand icon >, and then click View payload View icon for the part of the integration flow that failed.
        A mouse cursor hovers over the > icon in a milestone that appears in the activity stream

    4. Review the payload and take the appropriate action.

      For example, if a 404 error occurred, check the configuration of the connection.