collinmcnulty opened a new issue, #25252: URL: https://github.com/apache/airflow/issues/25252
### Description It would be great if every scheduler, webserver, worker, and triggerer had their own UUID that they emit as part of logs so that when logs from multiple components are put together in a log search tool you can easily track the logs from a specific component. I would suggest the new UUID 7 so that they can be sorted by start time. There's a similar argument to be made for giving each task instance a UUID, so depending on discussion here I may open a separate issue for that. ### Use case/motivation Although it is possible to enrich Airflow logs with information about their source using many log aggregators, this still falls a bit short. For instance, if a scheduler running in a Kubernetes pod fails a liveness check, the container will restart. The new scheduler will have the same pod name and container name within that pod as the old scheduler, so telling them apart requires knowing about the restart for other context. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
