Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.2.2
What happened and how to reproduce it?
Upon migrating to airflow 3.2.2 from 2.9.3 my airflow application stopped publishing logs to Azure App Insights. Running Airlfow on AKS.
For 2.9.3 version I had written a custom handler and attached it to the airflow.task logger and that enabled the tunnel to push the airflow task logs to Azure app Insights in the CustomEvents table
Now using the similar approach for 3.2.2, the logs are not being pushed to AppInsights.
Library used for AppInsights connection: azure-monitor-opentelemetry==1.8.9, azure-monitor-opentelemetry-exporter==1.0.0b55.
I tried putting in logs for the handler initialisation- the initialsation logs were shown but the emit() logs never showed up in any of the pods
What you think should happen instead?
No response
Operating System
No response
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.2.2
What happened and how to reproduce it?
Upon migrating to airflow 3.2.2 from 2.9.3 my airflow application stopped publishing logs to Azure App Insights. Running Airlfow on AKS.
For 2.9.3 version I had written a custom handler and attached it to the airflow.task logger and that enabled the tunnel to push the airflow task logs to Azure app Insights in the CustomEvents table
Now using the similar approach for 3.2.2, the logs are not being pushed to AppInsights.
Library used for AppInsights connection: azure-monitor-opentelemetry==1.8.9, azure-monitor-opentelemetry-exporter==1.0.0b55.
I tried putting in logs for the handler initialisation- the initialsation logs were shown but the emit() logs never showed up in any of the pods
What you think should happen instead?
No response
Operating System
No response
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct