Introduction to IDMC System Log Capture recipe

The recipe enhances the IDMC system visibility to enable effective monitoring, troubleshooting, and overall management of users' IDMC environments. It facilitates custom analytics and log retention requirements by enabling processes to systematically store internal IDMC log data to a user's cloud storage.

The IDMC System Log Capture recipe includes two taskflows designed to periodically extract system logging information from an IDMC organization and write it to a cloud storage location. The taskflows cover security logs and audit logs information.

These taskflows are designed to run periodically, with the default schedule assuming that the taskflows will run once a day and extract log information from the previous day. For example, if the taskflows run at 1 AM on April 11, they will extract log data from midnight April 9 to midnight April 10. With proper configuration, they can retrieve data from any IDMC organization or sub-organization, not necessarily residing in the same organization from which the log information is extracted.

The target location and type, such as AWS, Azure, Google, or Oracle, are determined by the connection object assigned to the taskflow’s mapping task, along with the target load path provided in the in_tgtPath input parameter.

This recipe is designed to run on Linux because it employs shell scripts to manage staging files. It utilizes both Data Integration and Application Integration, and it is not compatible with a serverless Application Integration server.