Parsing Audit Logs in Foundry—Identifying Projects

Ask the Community
1

Hi everyone,

I’m currently working on parsing the Audit Logs (2.0) in Foundry and have found that the sheer volume of data is overwhelming. One of the significant challenges I’m facing is identifying which project each log entry belongs to or refers to.

For example, when reviewing the logs, I cant see a clear way to trace entries back to their respective projects. This is important as we would like to track user activities based on project.
(a user can have access to several projects)
If any of you have experience tackling this issue, I’d greatly appreciate your insights or tips!

Additionally, if you’ve resolved other common challenges related to Audit Logs, I’d love to hear about those too.

Looking forward to learning from your experiences!

Thanks in advance for your help!

Best,
Ilan

2

Looking at the JSON objects in the request_params and result_params fields, you should be able to find some RIDs of the affected resources. Using these, you should be able to track down the projects in which these resources reside by hitting the getPath endpoint.

Docs for this endpoint are linked here: [REDACTED]/workspace/documentation/developer/api/compass/services/CompassService/endpoints/getPath

However, this still doesn’t solve the issue of identifying the workshop that associated with the functions and actions being triggered by the user.