-
Notifications
You must be signed in to change notification settings - Fork 177
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
astronomer-cosmos to send openlineage events to s3 bucket or cloudwatch logs #1423
Comments
Currently, there is no direct functionality or documented example in the Cosmos codebase for sending OpenLineage events directly to AWS S3 or CloudWatch. However, you can achieve this by customizing the OpenLineage event handler to redirect events to your desired storage. Here's a general approach you can take:
This approach requires some custom development, as there isn't a built-in feature in Cosmos for this specific use case. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Cosmos support openlineage See docs: https://astronomer.github.io/astronomer-cosmos/configuration/lineage.html To send event at remote location you have to setup transport configuration accordingly See docs: https://airflow.apache.org/docs/apache-airflow-providers-openlineage/stable/guides/user.html I tried to find docs to setup transport for s3 and found something here https://openlineage.io/docs/client/java/configuration/#s3 but this is for java client. But I feel there should be way to upload lineage to cloud. @tatiana / @pankajkoti do you know if uploading lineage to cloud work natively in Cosmos or not? |
Thanks for following up on this, @pankajastro ! Yes, all you wrote seems accurate. @mobuchowski could you confirm if there are any limitations with the S3 transport option in Python/Airflow? I improve our OpenLineage docs to highlight limitations regarding which dbt adaptors are supported: #1431 @bhawesh490 since you created #1430, is it correct to assume we can close this ticket? |
Thanks team
Yes you can close this issue
…On Fri, 27 Dec, 2024, 2:37 pm Tatiana Al-Chueyr, ***@***.***> wrote:
Thanks for following up on this, @pankajastro
<https://github.com/pankajastro> ! Yes, all you wrote is accurate.
I improve our OpenLineage docs to highlight limitations regarding which
dbt adaptors are supported: #1431
<#1431>
@bhawesh490 <https://github.com/bhawesh490> since you created #1430
<#1430>, is it
correct to assume we can close this ticket?
—
Reply to this email directly, view it on GitHub
<#1423 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOBV5EO7SB3JJ3K2ALICS432HUKFNAVCNFSM6AAAAABUDDUZJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRTGQ4DMOBVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi
Team i am using astronomer-cosmos to create dags for my client projects.
This is running in aws managed airflow environment.
We want to send the open lineage events to the s3 bucket and later on we can consume those events from s3 and push it to aws datazone .
Can you provide some sample snippets to accomplish this?
The text was updated successfully, but these errors were encountered: