OIC Gen 3 – Tracing Levels

 In Oracle Integration Cloud (OIC), tracing levels control how much execution information is captured for an integration instance. The three levels are:

Tracing Level	Data Retention	What is Logged	When to Use
Production	32 days	Logs the integration flow/actions with limited payload logging	Normal production operation
Audit	8 days	More detailed tracing, including external payloads	Troubleshooting and monitoring
Debug	24 hours	Most detailed tracing; logs all actions, including actions inside loops	Detailed troubleshooting/development

1. Production

Production is the normal/default level for production integrations.

• Execution data is retained for 32 days.
• Logs the overall integration flow/actions.
• Provides less detailed information than Audit or Debug.
• Suitable when the integration is running normally.
• Logs only Invoke/logger actions 

Short answer:

“Production tracing is used for normal production execution. It retains execution data for 32 days and provides basic flow-level logging without the detailed payload information available in higher tracing levels.”

2. Audit

Audit provides more detailed information than Production.

• Execution data is retained for 8 days.
• Logs the same flow-level information as Production.
• Also provides external payload logging, which is useful when troubleshooting data exchanged with external applications.

Short answer:

“Audit tracing is mainly used for troubleshooting because it provides more execution details and captures external payload information. The data is retained for 8 days.”

3. Debug

Debug is the most detailed tracing level.

• Data is retained for only 24 hours.
• Provides the same information as Audit.
• Additionally logs all actions within loops, making it useful for detailed troubleshooting.
• Because it generates much more execution information, it should generally be used temporarily.

Short answer:

“Debug tracing provides the highest level of execution detail. It logs actions inside loops in addition to the Audit-level information, but the data is retained only for 24 hours.”

Quick way to remember

Production → Audit → Debug

32 days → 8 days → 24 hours

Less detail → More detail → Maximum detail

How to change the tracing level

From the OIC Console, you can modify tracing for an integration without changing the integration design:

Integration → Actions/Options → Configure → Modify Tracing Level

So, if an interviewer asks:

“How would you troubleshoot an OIC integration that is working in Production but you cannot see enough execution details?”

“To troubleshoot temporarily increase the integration's tracing level from Production to Audit or Debug depending on the required level of detail. And reproduce the issue, analyze the instance activity and payload information, and then reduce the tracing level after troubleshooting.”