seanghaeli opened a new pull request, #66379:
URL: https://github.com/apache/airflow/pull/66379

   ## Summary
   
   Enable callback logs (deadline alerts, SLA notifications, etc.) to be 
uploaded to remote storage (S3, GCS, etc.) so they are visible in the Airflow 
UI when remote logging is configured.
   
   Key change: make `ti` optional in `RemoteLogIO.upload()` protocol and 
`upload_to_remote()` since callbacks don't have a task instance. The 7 
providers that ignore `ti` (S3, GCS, CloudWatch, WASB, OSS, HDFS, Alibaba) work 
immediately. Elasticsearch and OpenSearch now handle the `ti=None` case 
gracefully (log a warning and skip upload since they need TI for log ID 
rendering).
   
   ## Changes
   
   - Make `ti` optional (`RuntimeTI | None = None`) in `RemoteLogIO.upload()` 
protocol and `upload_to_remote()`
   - Update Elasticsearch and OpenSearch provider `upload()` signatures to 
match protocol
   - Add `_upload_logs()` to `CallbackSubprocess.wait()`, delegating to 
`upload_to_remote` with error handling
   - Wire up `_remote_logging_conn(client)` in `_configure_logging()` so remote 
log handler processors are initialized
   - Add unit tests for callback log upload behavior
   
   ## Related
   
   - Follows #65269 (callback supervisor comms handlers)
   - Prerequisite for callback log visibility in the UI


-- 
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