Hello, We've been recently looking into making the Airflow error messages more actionable and succinct, as per user feedback from the Airflow Debugging Survey (September 2024).
In regards to the same, your guidance, thoughts, concerns to below points would be deeply appreciated! 1. Ongoing discussion/brainstorming at: https://github.com/apache/airflow/issues/43171 2. TLDR of #43171 is that so for we've the following ideas: - We can introduce Airflow Error Codes (e.g. AERR001) and map them to corresponding "Commonly Observed Causes". Refer comment for samples: https://github.com/apache/airflow/issues/43171#issuecomment-2444113421 - We can make error code (or error ID) a mandatory param for AirflowException (and similar), then use it to produce OTEL metrics (e.g. counter or histogram for AERR001, etc). Refer comment for details: https://github.com/apache/airflow/issues/43171#issuecomment-2445213423 3. We've also been recommended Google's guide to writing error messages by GitHub user *hterik* (kudos!): https://developers.google.com/tech-writing/error-messages 4. PR with a mapping of few Airflow error codes (simply treat this PR as a primer): https://github.com/apache/airflow/pull/44616/files Based on the outcome of this discussion, I suppose we can plan next steps (voting or lazy consensus or so). Thank you for your time. Regards, Omkar
