Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging file are not stored in the centrlized folder #86

Open
sepidetari opened this issue Jul 13, 2018 · 6 comments
Open

Logging file are not stored in the centrlized folder #86

sepidetari opened this issue Jul 13, 2018 · 6 comments

Comments

@sepidetari
Copy link
Collaborator

sepidetari commented Jul 13, 2018

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.

@guruprasads7
Copy link
Collaborator

@sepidetari, You can use this to find where the changes happened using git log -p pom.xml.

@prasanthhs
Copy link
Contributor

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.

@sepidetari
Copy link
Collaborator Author

sepidetari commented Jul 14, 2018

@prasanthhs it is also a microservice, so it is created in web client project folder like others.

@prasanthhs
Copy link
Contributor

@sepidetari It dumps all logs on console. Even if pom setting is WARN, all logs (Debug, Warn , Info etc) are dumped.

@sepidetari
Copy link
Collaborator Author

@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 :)

@prasanthhs
Copy link
Contributor

@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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants