In OutSystems 11, developers could leverage GetRequestKey to correlate custom application logs with platform logs. In ODC, there is currently no supported way to access the runtime request identifier (Request ID / Trace ID) that appears in ODC platform logs.

Many customers implement custom auditing and logging solutions to capture business events, troubleshooting information, integration payloads, and operational diagnostics that are not covered by platform logging. 

Without access to the ODC request correlation identifier, it is difficult to connect custom logs with platform-generated logs during incident investigation and support activities.

Problem

When analysing issues, developers and support teams often need to combine:

• ODC platform logs
• Custom audit logs
• Custom application diagnostics
• Integration and business process traces

Currently, there is no straightforward way to correlate these data sources using a common request identifier.

Proposed Solution

Expose the current runtime Request ID / Trace ID through a built-in ODC API or System action, similar to the GetRequestKey capability available in OutSystems 11.

Example:

GetCurrentRequestId()

or

GetCurrentTraceId()

The returned value should match the identifier used internally by ODC platform logs so that developers can store it in:

• Custom audit tables
• Application logs
• Observability platforms
• External monitoring solutions
• Support diagnostic records

Use Cases

1. Audit Log Correlation
   Store the ODC Request ID in a custom audit table, allowing support teams to quickly find the corresponding platform log entries.
   
   
2. Enhanced Application Logging
   Capture additional business and technical details not supported by platform logs while maintaining full traceability.
   
   
3. Customer Support
   When customers provide an audit record or transaction ID, support teams can immediately correlate the request with ODC logs.
   
   
4. Integration Troubleshooting
   Follow a request across custom logging, integrations, business logic, and platform logs using a single correlation identifier.
   
   
5. External Observability Platforms
   Forward logs to SIEM and observability tools while preserving correlation with ODC runtime logs.

Business Value

• Faster incident investigation
• Reduced support effort
• Better observability and diagnostics
• Easier adoption of enterprise logging practices
• Feature parity with a commonly used OutSystems 11 capability
• Improved integration with external monitoring and audit solutions

Additional Context

Even when customers do not retain ODC logs beyond the default retention period, the correlation between custom audit records and platform logs is extremely valuable during the retention window. For customers that implement Analytics Streaming or external log retention, the value becomes even greater, enabling long-term traceability across multiple logging systems.