potiuk commented on issue #29949: URL: https://github.com/apache/airflow/issues/29949#issuecomment-1463700073
> It could be that rather than wanting more flexibility for email within Airflow, moving to something like the [OpenTelemetry Events API](https://opentelemetry.io/docs/reference/specification/logs/event-api/) makes more sense. Yes. That would follow very well our current effort to turn Airflow as an extensible platform where rather than implementing integrations and define our own ways of doing things we switch to existing "open" APIS - we already have OpenTelemetry (not events API) and OpenLineage approved. Adding OpenTelemetry Events API seems like a natural extension of it. Rather than using that in UI, I'd expose options to configure it in a way the Events API would support, so that rather than having to configure it in DAG code or UI, to get it more confiigurable on deployment level. -- 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]
