Workflow for Monitoring Integrations

Initial Monitoring Tasks

Before an automation solution goes live in production, optimize your monitoring workflow by completing a few tasks.

You might need to complete some tasks again when your organization prepares to release a major update to an automation solution.

Task	More information
Complete performance testing	See Measure an Integration's Performance.
Complete load testing	Check the scalability of a new automation solution by performing load testing. Load testing shows you how the automation solution will perform in a real-world scenario. For example, how will your order creation solution handle Black Friday? After completing load testing, measure performance. See Measure an Integration's Performance.
Prepare to go live	Document the automation solution, including its name, its use, the applications and connectivity agents that are involved, and contact names with backups for who gets involved and informed in the event of a failure. See View the Dashboard.
Update custom monitoring tools	If you maintain custom monitoring tools, determine whether to update them for the new automation solution. See About Building Your Own Observability Tools.
Choose start times intentionally	For schedule integrations, make sure the start time doesn't conflict with other integrations. For example, don't start twenty schedule integrations at 5 PM. Instead, stagger the start times. See View the Calendar of Schedule Integration Runs.
Set up notifications	Notifications provide daily or hourly emails about failures or the overall health of all your integrations. See Send System Status Reports with Notification Emails.
Plan the hand-off	If you'll monitor your own automation solution, skip this row. However, if you'll monitor another person's automation solution, determine a hand-off schedule. For example, when the automation solution goes live, or after the automation solution runs successfully in production for a period of time. Setting expectations from the beginning helps ensure the successful launch of a new business process automation.
Verify that updates don't impact performance	After you version and update an automation solution, compare the average running times of the previous and new solutions to ensure that you haen't introduced performance regressions. See Determine an Integration's Typical Processing Times.

Daily Monitoring Tasks

Organizations typically perform these tasks at least daily, often at predetermined times.

Task	More information
Check whether integrations experienced errors	Find Integrations That Experienced Errors
Check whether integrations timed out or were canceled	Find Integrations That Timed Out or Were Aborted
Check for performance issues	Troubleshoot slow-running integrations and verify that integrations meet your organization's performance requirements. See Measure an Integration's Performance.
Identify recent updates	When an automation solution stops working as expected, an inadvertent update could be to blame. Check the audit history to find out what happened. See Check the Audit History for an Integration or Other Component.
Determine why fewer integration instances are running	Fewer Integration Instances Ran Than Usual
Check whether connectivity agents are available	If a connectivity agent isn't available, any integrations that use the agent fail. Inform the administrator who is responsible for the connectivity agent if any agents go down. See Monitor Agents.
Identify connections with the most errors	Find the Connections with the Most Errors

Occasional Monitoring Tasks

Routine analysis work supports operational excellence. Use your organization's operating procedures to determine how often you complete these tasks. For example, you might complete some tasks weekly, monthly, or quarterly.

Task	More information
Check performance	Measure an Integration's Performance
Check tracing levels	Check an Integration's Tracing Level
Stay within the limits	Make sure that your organization's active integrations stay below the limit. On the Dashboards page, see the numbers in the Active integrations box. To explore all service limits, see Service Limits in Provisioning and Administering Oracle Integration 3.
Confirm the staggered start times of schedule integrations	If too many schedule integrations start at the same time, they might experience contention. Ease the contention by staggering the start times. See View the Calendar of Schedule Integration Runs.
Check the status of all components	See the Current Status of All Integration Components
Update documentation	Periodically review the documentation for your automation solution and make updates for organizational changes and employee turnover.