Skip to content

Add Event Log summary to Task/Dag Overview tabs #41312

Open

Description

@fritz-astronomer

Description

@o-nikolas @vincbeck

During the town hall meeting - it was brought up that important scheduler events in the Event Tab may not be easily visible or discoverable, with folks used to looking at the task logs.

One idea, was to have a count of Event Logs associated with a particular task run - e.g. [Event Logs (5)]

Use case/motivation

No response

Related issues

#40967
#40867

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. added
    area:UIRelated to UI/UX. For Frontend Developers.
    on Aug 7, 2024
  2. removed
    needs-triagelabel for new issues that we didn't triage yet
    on Sep 27, 2024
  3. bbovenzi commented on May 6, 2025

    @bbovenzi
    Contributor

    Instead of the count in the tab, we can do this on the dag/task overview pages. Although event/audit logs can still be inconsistent on what is recorded.

  4. added this to the Airflow 3.1.0 milestone on May 6, 2025
  5. changed the title [-]Airflow UI Event Log Notification[/-] [+]Add Event Log summary to Task/Dag Overview tabs[/+] on May 6, 2025
  6. added
    priority:lowBug with a simple workaround that would not block a release
    and removed on May 6, 2025
  7. naseemshah commented on Jul 14, 2026

    @naseemshah
    Contributor

    i'd like to work on this, and I want to float a slightly richer UX.

    How about something like "Smart Logs/ Unified Logs" and a filter menu for log type?

    [2026-07-14 10:02:01] INFO - Starting attempt 1 of 3
    [2026-07-14 10:02:05] INFO - Executing <Task(PythonOperator): extract>
      ─── ⚑ 1 event · 10:02:05 · task started (scheduler) ───────────────
    [2026-07-14 10:04:31] INFO - Processing batch 3/12...
      ─── ⚑ 2 events · 10:05:10 · heartbeat timeout, retry scheduled ────
    [2026-07-14 10:05:12] INFO - Received SIGTERM. Terminating...
    

    Something like this but with interactive rich log lines?

    Markers are collapsed one-liners, expandable to full event details. Since the Logs tab already has source and log-level filters, audit events could simply appear as an additional source there — off by default or toggleable, so nothing changes for users who don't want it.

  8. bbovenzi commented on Jul 14, 2026

    @bbovenzi
    Contributor

    Yeah that sounds interesting. Feel free to comment screenshots/videos of a demo here first for us to experiment with the UX before you work on a full pull request

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:UIRelated to UI/UX. For Frontend Developers.contributors-workshopIssues that are good for first-time contributor's workshopkind:featureFeature Requestspriority:lowBug with a simple workaround that would not block a release

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions