We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After some time spent deploying NodeZoo with following deploying structure:
I found that it is very hard to check logs and see what/why something is happening with a particular micro-service.
I think we will need a way to centralize all logs - best way seems with Logstash/ElasticSearch
The text was updated successfully, but these errors were encountered:
It seems that the approach to follow will be:
Sorry, something went wrong.
Looks solid. @pelger any thoughts here?
mirceaalexandru
No branches or pull requests
After some time spent deploying NodeZoo with following deploying structure:
I found that it is very hard to check logs and see what/why something is happening with a particular micro-service.
I think we will need a way to centralize all logs - best way seems with Logstash/ElasticSearch
The text was updated successfully, but these errors were encountered: