Forum Discussion
Fabric pipelines audit
- 21 days ago
Hi Eleanordum93,
I would recommend creating a UDF that accepts the things you want to log as parameters, and then saves them to a warehouse or SQL database. THen you can call that UDF from the pipeline (or from a notebook, or from anywhere else really) to log something.
This is better than using a notebook because it doesn't require a spark session to be created so will be cheaper on compute/CU usage.
Hello Eleanordum93,
You may not need a notebook for this. Fabric Workspace Monitoring provides pipeline and activity-level execution logs, including status, timestamps, activity name and pipeline run ID.
You can query these logs and persist the fields you need into your own audit table.
Microsoft docs:
Enable workspace monitoring in Microsoft Fabric