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

   ### Apache Airflow Provider(s)
   
   elasticsearch
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-elasticsearch=6.5.0
   
   ### Apache Airflow version
   
   3.1.5
   
   ### Operating System
   
   ubuntu:22.04
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   k8s,helm
   
   ### What happened
   
   There was a problem with logging into ELK not working. 
   I updated the apache-airflow-providers-elasticsearch package to version 6.5.0
   Now that logging is working, when opening the DAG logs, the first line shows 
where this log is coming from, but the problem is that in the same line he 
writes the login and password to ELK, with which he searches in the index 
pattern. Do I think he shouldn't be there?
   
   ### What you think should happen instead
   
   I think that it should only indicate the source of receiving logs (for 
example, the host and port of ELK)
   
   ### How to reproduce
   
   1. Install apache-airflow-providers-elasticsearch=6.5.0
   2. Enable logging to ELK in airflow.cfg using the example below:
   
   `    [logging]
   
       remote_logging = True
   
       [elasticsearch]
   
       host = https://USER:[email protected]:9200
   
       json_format = True
   
       write_to_es = True
   
       target_index = elk_test_index
   
       index_patterns = elk_test_index*`
   
   3. Launch the DAG
   4. View its logs in the UI
   
   
   ### Anything else
   
   Sorry, I already disabled logging and couldn't provide screenshots.
   
   ### 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