Skip to content

Improve aggregate reingestion reporting #4121

Open

Description

Current Situation

#4074 modified reingestion workflows to skip Slack error reporting during the pull_data tasks, and instead report errors in aggregate in a task at the end of the Dagrun. Because a reingestion workflow can have >100 ingestion days, it's possible this aggregate message could contain links to 100s of logfiles in the worst case. Consequently the message is configured to only link the first 5 error logs.

There is also no context as to what the errors were in the Slack message itself, just the link to the log file for the failed task.

Suggested Improvement

It would be great to include information about the errors that were detected in the Slack message. In particular, when there is more than one failed reingestion day it would be very useful to know whether all the failed days encountered the same error, in which case it may not be necessary to investigate them individually.

We should weigh the benefits of presenting this information against the desire to keep the Slack notifications as brief as possible.

Additional context

Comment thread on the aggregate reporting PR which discussed this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    💻 aspect: codeConcerns the software code in the repository🟩 priority: lowLow priority and doesn't need to be rushed🧰 goal: internal improvementImprovement that benefits maintainers, not users🧱 stack: catalogRelated to the catalog and Airflow DAGs

    Type

    No type

    Projects

    • Status

      📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions