View runs logs

Bolt provides an overview of all the schedules configured in your Paradime workspace. You can use the Bolt app to view details of all schedules and run logs for each run.

Bolt Schedules list

The Bolt home screen lists all schedule names parsed, both UI-based and YML-Based.

Here you can view preview details of each schedule:

• Name: Name of the schedule

• Status: Current status of a schedule names

• Owner: The owner of the schedule (if configured)

• Cron Description: The time of day (UTC time) that the schedule runs, defined by cron configuration.

• Cron Configuration: The cron syntax of the scheduled run.

• Last run: Date and time of when the schedule was last triggered

• Next run: Date and time the scheduler will trigger next

• Until Next run: Time remaining until schedule triggers next

• Trigger Type: How your schedule is triggered (On schedule, On Run Completion)

• On Completion Configuration: Details on how your On Run Completion is configured (If applicable)

Inactive Schedules

Removing a schedules from the paradime_schedules.yml file or deleting a UI-based schedule will mark these as inactive. A schedule can become inactive if:

• The schedule name is deleted

• The name of a schedule is modified

By clicking on the schedule name now inactive, you will be able to view the configuration of a schedule before it became inactive as well as all historical runs and logs. An inactive schedule cannot be manually triggered from the UI.

Schedule details

To view details of a specific schedule and all historical runs, navigate to the Bolt application and click on the schedule name.

Here you can view the schedule configuration details:

Schedule name overview​

• Next run: time the scheduler will trigger the selected schedule name

• Owner: The schedule's owner (if configured)

• Trigger Type: How the schedule is being triggered (Scheduled run or On run completion)

• Branch: The branch name used when running the schedule (if no branch is configured in the paradime_schedules.yml paradime will use your default branch)

• dbt™️ version: The dbt™️ version used in the production environment

• Notify: The details of where paradime will send notifications for the selected schedule name (if configured)

• Commands: The dbt™️ commands executed in the schedule

Run History​

In the Run History section, you can view all the run executed for the selected schedules including:

• Status: status of the specific runID

• Trigger: if the runID was manually triggered or if it is a run triggered as per the cron figuration by the paradime scheduler

• Branch and commit: the branch name and commit SHA used when running the schedule

• Timing: details of when the runId was executed and how long it took to complete

• RunID: unique identifier of the run

Run Details

To view details about a specific run ID of a schedule, click on the run ID. This view offers various tools to better understand schedule run performance, such as:

Insights

• DAGs View: Examine how your scheduled run commands are being executed.

• Model Timeline: View the order and execution time of each model in a specific run ID.

This layout provides a concise and clear explanation, making it easier for users to understand the tools available for analyzing schedule run performance.

Logs and Artifacts

View additional metadata associated with a specific run ID, such as:

• Run Logs: A detailed record of each command executed during a scheduled run, including the execution summary, console logs, and debug logs.

• Source Freshness: Information about the freshness of data sources used in the run.

• Artifacts: Files generated during a dbt scheduled run, including run SQL files, compiled SQL files, manifest files, .json, etc. They provide insights into what was executed and how, enabling you to analyze the output of your dbt runs.