Adeptia Connect logs messages during the execution of an activity on a microservice to help you monitor and troubleshoot the application. The application writes these logs to standard output (stdout) and standard error (stderr). Kubernetes then reads the logs and creates a separate log file for each Microservice.
Adeptia Connect bundles a tool, EFK, that can help you view the logs as and when required. This tool is constituted of three components – Elastic search, Fluentd, Kibana – each working in tandem to serve a common purpose of working with and viewing the logs.
All the three components have their specific job to perform to enable you view the logs. Here's how it works.
- Fluentd collects the logs from Kubernetes and pushes them to Elastic search.
- Elastic search creates index doc for all the logs.
- Kibana looks into the Elastic search and acts as a UI to show the logs.
How we've configured EFK to let the client configure external logging.