The easiest way to launch the UI from the command line during local development is to run:
This command launches both the Dagster webserver (which serves the UI) and the Dagster daemon, allowing you to start a full local deployment of Dagster from the command line.
The command will print out the URL you can access the UI from in the browser, usually on port 3000.
When invoked, the UI will fetch definitions - such as assets, jobs, schedules, sensors, and resources - from a Definitions object in a Python module or package or the code locations configured in an open source deployment's workspace files. Refer to the Code location documentation for more info.
You can also launch the webserver by itself from the command line by running:
Note that several Dagster features, like schedules and sensors, require the Dagster daemon to be running in order to function.
Description: This page, also known as the "factory floor", provides a high-level look at the activity in your Dagster deployment, across all code locations. This includes information about runs, jobs, schedules, sensors, resources, and backfills, all of which can be accessed using the tabs on this page.
Accessed by: Clicking Overview in the top navigation bar
Description: The Asset catalog page lists all assets in your Dagster deployment, which can be filtered by asset key and/or asset group. Clicking an asset opens the Asset details page for that asset. You can also navigate to the Global asset lineage page, reload definitions, and materialize assets.
Accessed by: Clicking Assets in the top navigation bar
Description: The Run details page contains details about a single run, including timing information, errors, and logs. The upper left pane contains a Gantt chart, indicating how long each asset or op took to execute. The bottom pane displays filterable events and logs emitted during execution.
In this page, you can:
View structured event and raw compute logs. Refer to the run logs tab for more info.
Re-execute a run using the same configuration by clicking the Re-execute button. Related runs (e.g., runs created by re-executing the same previous run) are grouped in the right pane for easy reference
Description: Located at the bottom of the Run details page, the run logs list every event that occurred in a run, the type of event, and detailed information about the event itself. There are two types of logs, which we'll discuss in the next section:
Description: Structured logs are enriched and categorized with metadata. For example, a label of which asset a log is about, links to an asset’s metadata, and what type of event it is available. This structuring also enables easier filtering and searching in the logs.
Accessed by: Clicking the left side of the toggle next to the log filter field
Description: The Schedules page lists all schedules defined in your Dagster deployment, as well as information about upcoming ticks for anticipated scheduled runs. Click a schedule to open the Schedule details page.
Description: The Schedule details page contains details about a single schedule, including its next tick, tick history, and run history. Clicking the Test schedule button near the top right corner of the page allows you to test the schedule.
Description: The Sensors page lists all sensors defined in your Dagster deployment, as well as information about the sensor's frequency and its last tick. Click a sensor to view details about the sensor, including its recent tick history and recent runs.
Description: The Sensor details page contains details about a single sensor, including its next tick, tick history, and run history. Clicking the Test sensor button near the top right corner of the page allows you to test the sensor.
Description: The Resource details page contains detailed information about a resource, including its configuration, description, and uses. Click the tabs below for more information about the tabs on this page.
Accessed by: Clicking a resource in the Resources page
Description: The Configuration tab contains detailed information about a resource's configuration, including the name of each key, type, and value of each config value. If a key's value is an environment variable, an Env var badge will display next to the value.
Description: The Uses tab contains information about the other Dagster definitions that use the resource, including assets, jobs, and ops. Clicking on any of these definitions will open the details page for that definition type.
Description: The Backfills tab contains information about the backfills in your Dagster deployment, across all code locations. It includes information about when the partition was created, its target, status, run status, and more.
Description: The Jobs page lists all jobs defined in your Dagster deployment across all code locations. It includes information about the job's schedule or sensor, its latest run time, and its history. Click a job to open the Job details page.
Accessed by: Clicking Overview (top nav) > Jobs tab
Description: The Launchpad tab provides a configuration editor to let you experiment with configuration and launch runs. Note: For assets, this tab will only display if a job requires config. It displays by default for all op jobs.
Accessed by: On the Job details page, clicking the Launchpad tab
Description: The Partitions tab displays information about the partitions associated with the job, including the total number of partitions, the number of missing partitions, and the job's backfill history. Note: This tab will display only if the job contains partitions.
Accessed by: On the Job details page, clicking the Partitions tab
Description: The Code locations tab contains information about the code locations in your Dagster deployment, including their current status, when they were last updated, and high-level details about the definitions they contain. You can reload Dagster definitions by:
Clicking Reload all to reload all definitions in all code locations
Clicking Reload next to a specific code location to reload only that code location's definitions
Clicking Deployment in the top navigation bar
On the Deployment overview page, clicking the Code locations tab