Logging and Monitoring

Overview

Effective monitoring is key toensuring the reliability and timeliness of your data processing tasks.

Empower provides robust tools for monitoring your data estate, enabling you to track their execution status, performance, and any issues that may arise. From , we detail how users can leverage the flow log page in Empower to monitor their data flows, focusing on aspects such as start times, run IDs, durations, and statuses.

Run Logs

Empower provides logging capabilities to track the various current and historical runs of any data flow.

Navigate to a specific flow's logs by clicking "View Runs" for that flow.

Click "View Runs" to navigate to any flow's log table.

Click "View Runs" to navigate to any flow's log table.

A log table for a data flow.

A log table for a data flow.

Run ID: Upon initialization a run is assigned a unique Run ID. This identifier is crucial for tracking specific instances of runs programmatically, especially when diagnosing issues or auditing data processing tasks.

Start Times: This indicates when the run execution began. Tracking start times helps in understanding the schedule adherence and identifying any delays in execution.

End Time: This indicates when the run execution completed, either successfully or in failure.

Duration: Duration tracks the length of time a run took to complete. Significant deviations from the norm can indicate problems or inefficiencies in data acquisition, processing, or publishing.

Status: Status (e.g., “Success,” “Failed,” “Running”) provides immediate insight into a run's current or completed state.