RoyLee1224 commented on PR #54252:
URL: https://github.com/apache/airflow/pull/54252#issuecomment-3193397977

   Hi all, thanks for such a productive discussion.
   
   As I'm not a heavy Airflow user myself, I've been trying to imagine the 
kinds of problems this new Calendar View could help solve from a user's 
perspective.
   
   My thinking is that if we can align on the key questions users will ask, we 
can better shape the final design. Here are a few situations that come to mind:
   
   ## Use Cases
   
   ### 1. A quick "Health Check" -  "How has my Dag been running lately?"
   Just a quick glance to see if the past month/week was mostly stable (green) 
or if there are emerging issues (red/yellow).
   
   ### 2. Spotting problems after a change - "I deployed an update to this Dag. 
Did it cause any new problems?"
   Compare the Dag's "before vs. after" for version changes.
   
   ### 3. Understanding the severity of a problem - "I see some failures. Which 
day needs my immediate attention?"
   It seems important to help users distinguish between a minor issue (e.g., 1 
failure out of 20 runs) and a critical outage (e.g., 5 failures out of 5 runs). 
Both are problems, but the second one is clearly more severe.
   
   ## Proposed Solution: Start Clean, Provide Detail on Demand
   ### Default View: 
   Keep it simple and clean, focusing on the primary state (Success, Failed, 
Mixed). With optional "Show Total Runs" button.
   ### Tooltips for Severity Assessment: 
   When a user hovers over a day/hour, the tooltip can display a mini bar chart 
or stacked bar chart showing the success vs. failure counts. I think this is 
more intuitive than a pie chart, especially when comparing days with different 
total runs.
   
   ### Filter Bar: 
   This would allow users to ask very specific questions to find exactly what 
they're looking for. For example:
   - Filter by Success Rate (e.g., > 50% or < 20%).
   - Filter by Total Runs (e.g., > 10 or < 5).
   
   
   This is just my current line of thinking, and I'm very curious to hear from 
the maintainers and other experienced users. Do these scenarios make sense? Are 
there other important situations I might be missing?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to