Page Comparison

Adeptia Connect integrates EFK for logging, and Prometheus and Grafana for monitoring purposes. The image given below depicts how EFK, and Prometheus and Grafana are used with Adeptia Connect for logging and monitoring functions.

• To use EFK (Elasticsearch, Fluentd, Kibana) as a logging tool while deploying Adeptia Connect v4.0, set the value for the property global.config.logging.enabled in values.yaml file to true. Once set to true, the EFK stack is automatically deployed.

You can, however, opt out of using these tools, and use other tools of your preference. 

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. The points below describe the logging mechanism.

• 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. Here's how EFK works.

Image Modified

• 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.

• Most of the centralized logging tool can read the logs written by Kubernetes. In case you use some other centralized logging tool they can follow the documentation of respective tool or use their internal expertise o read log files from Kubernetes and configure their tool and design dashboard.