-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dagster-airlift][federation-tutorial] Observe section federation tutorial #25892
[dagster-airlift][federation-tutorial] Observe section federation tutorial #25892
Conversation
Graphite Automations"Add a 'docs-to-migrate' label to PRs with docs" took an action on this PR • (11/13/24)1 label was added to this PR based on Christopher DeCarolis's automation. |
docs/content/_navigation.json
Outdated
@@ -949,6 +949,10 @@ | |||
{ | |||
"title": "Part 1: Setup upstream and downstream Airflow instances", | |||
"path": "/integrations/airlift/federation-tutorial/setup" | |||
}, | |||
{ | |||
"title": "Part 2: Observe dag lineage in Dagster", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"title": "Part 2: Observe dag lineage in Dagster", | |
"title": "Part 2: Observe DAG lineage in Dagster", |
@@ -0,0 +1,208 @@ | |||
# Airflow Federation Tutorial: Observing multiple Airflow instances | |||
|
|||
At this point, we should have finished the [setup](/integrations/airlift/federation-tutorial/setup) step, and now we have the example code setup with a fresh virtual environment, and our two Airflow instances running locally. Now, we can start writing Dagster code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point, we should have finished the [setup](/integrations/airlift/federation-tutorial/setup) step, and now we have the example code setup with a fresh virtual environment, and our two Airflow instances running locally. Now, we can start writing Dagster code. | |
At this point, you should have finished the [setup](/integrations/airlift/federation-tutorial/setup) step, and now you have the example code in a fresh virtual environment, and two Airflow instances running locally. Now, let's start writing Dagster code. |
|
||
## Observing the Airflow instances | ||
|
||
We'll start by creating asset representations of our DAGs in Dagster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll start by creating asset representations of our DAGs in Dagster. | |
We'll start by creating asset representations of our Airflow DAGs in Dagster. |
|
||
### Observing the `warehouse` Airflow instance | ||
|
||
Next, we'll declare a reference to our `warehouse` Airflow instance, which is running at `http://localhost:8081`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I requested changes above of we -> you
, but let's just make sure there's consistency across guides.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with some nits.
We need to make sure we're consistent in how we talk to the user, whether that be us saying "you" directly, which I believe we do in other docs, or "we".
fc3bfd8
to
56dc056
Compare
ea3067a
to
2390f28
Compare
56dc056
to
e4270a2
Compare
2390f28
to
d038556
Compare
e4270a2
to
5e67354
Compare
d038556
to
3eb8689
Compare
2ac9632
to
13ff868
Compare
3eb8689
to
9b8354a
Compare
13ff868
to
09b59d8
Compare
9b8354a
to
2adfd07
Compare
) | ||
# end_lineage | ||
|
||
defs = Definitions(assets=[load_customers, customer_metrics_dag_asset]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The final Definitions
object is missing the sensor registrations that were defined earlier. To ensure both DAGs are properly monitored, the sensors should be included:
defs = Definitions(
assets=[load_customers, customer_metrics_dag_asset],
sensors=[warehouse_sensor, metrics_sensor]
)
This ensures that both the warehouse and metrics DAGs will be monitored for new runs.
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
09b59d8
to
ee91104
Compare
2adfd07
to
71aa819
Compare
ee91104
to
64722c3
Compare
71aa819
to
72e4fe5
Compare
64722c3
to
b896f9c
Compare
72e4fe5
to
48e9247
Compare
b896f9c
to
1821ae4
Compare
48e9247
to
86ce701
Compare
1821ae4
to
cb5258e
Compare
86ce701
to
3940172
Compare
cb5258e
to
31e1b1e
Compare
3940172
to
7da4baa
Compare
Summary & Motivation
How I Tested These Changes
Changelog