# Dagster

In this section, we provide guides and references to use the Dagster connector.

## Requirements

OpenMetadata is integrated with dagster up to version <a href="https://docs.dagster.io/getting-started" target="_blank">1.0.13</a> and will continue to work for future dagster versions.

The ingestion framework uses <a href="https://docs.dagster.io/_apidocs/libraries/dagster-graphql#dagster_graphql.DagsterGraphQLClient" target="_blank">dagster graphql python client</a> to connect to the dagster instance and perform the API calls.

You can find further information on the Kafka connector in the <a href="https://docs.open-metadata.org/connectors/pipeline/dagster" target="_blank">docs</a>.

## Connection Details

$$section
### Host $(id="host")

Pipeline Service Management URI. This should be specified as a URI string in the format `scheme://hostname:port`. E.g., `http://localhost:3000`.
$$

$$section
### Token $(id="token")

To Connect to Dagster Cloud.
- Log in to your Dagster account.
- Click on the `Settings` link in the top navigation bar.
- Click on the `API Keys` tab.
- Click on the `Create a New API Key` button.
- Give your API key a name and click on the `Create API Key` button.
- Copy the generated API key to your clipboard and paste it in the field.
$$

$$section
### Timeout $(id="timeout")

Connection Time Limit between OpenMetadata and Dagster Graphql API in seconds.

$$

$$section
### Strip Asset Key Prefix Length $(id="stripAssetKeyPrefixLength")

Number of leading segments to remove from asset key paths before resolving to tables.

**About Dagster Asset Keys:**

Dagster asset keys are path-like identifiers represented as arrays of strings (e.g., `["project", "environment", "schema", "table"]`). When OpenMetadata ingests Dagster pipelines, it tries to match these asset keys to table entities using the standard format: `database.schema.table` or `schema.table`.

**When to Use This Setting:**

If your Dagster asset keys include additional prefix segments beyond the database/schema/table hierarchy, use this setting to strip those prefixes. For example:
- Asset key: `["project", "environment", "schema", "table"]`
- Set value to `2` to strip `project` and `environment`
- Result: `schema.table` (matches OpenMetadata table entities)

Common use cases include stripping:
- Project/workspace identifiers
- Environment names (dev/staging/prod)
- Storage bucket/container prefixes

Default value is `0` (no stripping).

$$
