Hello team
I would like to ask about access logs in ODC.In some cases, an IP address fails to access an ODC application, and I would like to determine whether :- the request never reached the ODC environment, or- the request reached ODC but was rejected (for example, by some platform-level restriction)I checked the logs and traces available in the ODC portal, but I could not find any information about the source IP address of incoming requests.
Is this information intentionally not exposed due to OutSystems / ODC platform limitations?If so, is there any recommended approach to troubleshoot access issues from specific networks or locations?Any clarification or best practice would be appreciated.
Thank you.
Due to the documentation, you can use the audit trail export function to gather the source IP
Please check this https://success.outsystems.com/documentation/outsystems_developer_cloud/monitoring_and_troubleshooting_apps/audit_trail/
As mentioned above by Shingo in ODC, you can't see source IP addresses directly in the standard Logs/Traces views in the Portal — that's why you didn't find them there.
But yes, it's possible via the Audit Trail feature. The audit logs include the field Event_Request_SourceIp (the IP of the user/system that made the request).
How to get it:
@Shingo Lam @Bhanu Pratap
I see, so it can be checked using audit logs.Thank you for your explanation!
you are welcome
No problem, Happy to help
Hello,
This is a good question and a common challenge when troubleshooting access issues in ODC.
At the moment, source IP details are not exposed in ODC application logs or traces. This is largely intentional and tied to the platform’s cloud-native architecture: traffic typically passes through managed gateways, load balancers, and security layers before reaching the application, and client IPs are abstracted away for security and multi-tenant reasons.
As a result, it’s difficult to conclusively determine—using ODC logs alone—whether a request never reached the environment or was rejected at a platform or network layer.
Recommended approaches include:
Checking whether the client network has restrictions (corporate firewall, VPN, geo-blocking).
Validating access using the same IP via tools like Postman or curl.
Reviewing any custom security rules, integrations, or upstream proxies.
Raising a support ticket with OutSystems, providing timestamps, target URLs, and affected IP ranges—platform teams can investigate at the infrastructure level.
While limited, this is currently the best practice for IP-based access troubleshooting in ODC.