vrandakoolwal opened a new issue, #72093:
URL: https://github.com/apache/airflow/issues/72093

   ### 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?
   
   - [ ] 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]

Reply via email to