Centralized logging

In a Microservices architecture centralized logging plays a key role. it can be very useful when attempting to identify problems with your servers or applications, as it allows you to search through all of your logs in a single place. It is also useful because it allows you to identify issues that span multiple servers by correlating their logs during a specific time frame. Adeptia Connect logs messages during the execution of an activity to help you monitor and troubleshoot the application. You can use EFK for logging purposes. 

How the EFK logging works

• The application writes the logs to standard output (stdout) and standard error (stderr). 
• Kubernetes then reads the logs, and creates a separate log file for each microservice.
• EFK helps you view the logs as and when required. 

• Fluentd collects the logs from Kubernetes and pushes them into Elasticsearch. 
• Elasticsearch maintains the index of all the logs.

• Kibana is the UI where you can view the logs available in Elasticsearch.