My main argument is that we can achieve a lot by improving the existing Notes UX or through a custom UI plugin. Also, we should do more to improve the logs experience for you, Jens.
Let's exhaust those avenues before adding something else to core Airflow that needs to be maintained indefinitely. - Brent On Mon, Apr 27, 2026 at 3:10 PM Jens Scheffler <[email protected]> wrote: > Hi, > > as co-author also wanted to join-in the discussion but missed it so far. > > I'd also be very interested in the points that mainly Brent and > Constance are reluctant to. What are the main points that you do not > want to have? > > Mainly the idea is that the "Summary" (or better names welcome) is > machine (even LLM?) generated and is produced by code - read only for a > fast overview or even status. Notes are something very good for > additional "stuff" that a user wants to remark e.g. "Jens: Killed at 9AM > as not needed anymore" (so that nobody else comes along and restarts the > failed task - to maybe coordinate ops work). I thing User Notes and > machine generated "Summaries" should not over-write each other. > > Jens > > (also being one person who need to scroll through a lot of task logs > every days to fiddle the root casue of failures, and our logs are ~5k > lines long so always takes a few seconds to load to get too the end... > so I'd save a couple of hundret meters of mouse wheel each day if I > would have a summary) > > On 27.04.26 15:54, Kuettelwesch Marco (XC-AS/ESE6-ADA) via dev wrote: > > I understand the concerns about the notes and the headline may be a > little misleading. > > > > The primary goal is to improve the user experience for everyone. > > To support this, an operator could optionally generate a code-based > summary that helps users quickly understand the result. This should remain > optional, since not all operators are expected to support it out of the box. > > > > One idea is to add a new Web UI tab alongside the existing Audit Log, > Code, and Details tabs. > > This new tab could present a Markdown-based Task/DagRun Summary (or > Task/DagRun Report — naming is open for discussion) containing the > generated execution summary. > > > > We could also display the existing task and DagRun notes in the same > tab, so users can view both human-authored input and generated insights in > one place. > > The tab would only be shown when either a note or a generated summary > exists. > > > > Bringing both perspectives together would make it much easier to > understand what is happening with a task or DagRun, while keeping > user-written and system-generated content separated. > > > > What do you think? > > Marco > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
