Activator Monitoring features

Hi evrise,

To achieve a robust and audit-compliant tracking mechanism, you can implement custom logging as part of the pipeline or notebook execution flow triggered by Activator. This approach provides full control over the audit data captured and retained.

Logging Strategy:

* Insert a logging step at the beginning of each pipeline or notebook.

* Then capture the following key metadata: 

Timestamp using utcnow() to record the execution time. Environment context, such as workspace name, pipeline name, and run parameters, using System.Environment variables or expressions like pipeline() (for pipeline metadata). Initiator details, including pipeline().RunId and any user metadata available via parameterization or triggering context.

Recommended Logging Destinations:

* Delta Table in a Lakehouse – Ideal for scalable querying and long-term retention.

* Azure Log Analytics (Custom Logs) – Enables centralized monitoring and alerting integration.

* Azure Storage (Blob/Table) – Cost-effective raw log storage.

* SQL Database Table – Useful for structured querying and downstream reporting.

By embedding this logging mechanism within the execution flow, organizations can ensure all Activator-triggered processes are traceable, auditable, and compliant with internal or regulatory monitoring requirements.

Best Regards,

Hammad.