Open sepidetari opened 6 years ago
@sepidetari, You can use this to find where the changes happened using git log -p pom.xml.
Additionally, web client logging file does not seem to be created on linux. All logs are dumped on console and it does not obey logback-spring.xml. It always dumps debug and info logs.
@prasanthhs it is also a microservice, so it is created in web client project folder like others.
@sepidetari It dumps all logs on console. Even if pom setting is WARN, all logs (Debug, Warn , Info etc) are dumped.
@prasanthhs they are configured to dump logs in console and store them in file at the same time. We have checked them a few days ago and everything were working properly. If you had the issue by not saving the files (or any other issue regarding logs) previously you could have informed us earlier then we could solve it. But if you face it now, it is the reason that I opened this issue :)
@sepidetari We found the issue when we were debugging other problem related to chatbot display yesterday night. It is ok to leave it as an open issue for next team (or create new issue).
The configuration set up to store all the logs produced by microservices in a central folder has been changed, now each MS logs are stored in its own folder so produced logs can not be send to elasticsearch. because of the high number of commits pushed in master at the last days, I could not find the commit has caused this problem and the exact reason till now.