GitHub user PrithwishDas101 added a comment to the discussion: What is the use of OTEL Property otel_task_log_event ?
I'd separate two things here: emitting task-log events through Airflow's OpenTelemetry integration, and correlating ordinary task log lines with distributed traces. If you're ingesting the task log files directly, printing the active trace and span IDs can help your log backend correlate those records, provided the IDs are captured from the correct execution context. That is not necessarily the same pipeline as exporting logs as OpenTelemetry events. Before enabling `otel_task_log_event`, I'd check the configuration reference and implementation for your exact Airflow version to confirm what event it emits, where it is exported, and whether it includes the context you need. The name alone doesn't guarantee that it exports every task log line or automatically correlates raw log files. If you share the Airflow version and the relevant OpenTelemetry configuration, it should be possible to distinguish whether you need Airflow's log-event integration, direct log ingestion with trace IDs, or both. GitHub link: https://github.com/apache/airflow/discussions/60140#discussioncomment-18950010 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
