Centralized logging and monitoring

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.

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

• If you opt for EFK (Elasticsearch, Fluentd, Kibana) as a logging tool while deploying Adeptia Connect v4.0, the EFK stack is automatically deployed. 

• If you opt for Prometheus and Grafana as monitoring tools while deploying Adeptia Connect v4.0, the tools are automatically deployed. 

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.

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

  EFK configuration is not bundled with beta release. Adeptia team will help in the configuration in the respective customer environment.
• 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.

Monitoring

Once up and running, Adeptia Connect allows you to monitor the system and its execution environment holistically by using a monitoring tool. Here's how Adeptia Connect helps you do that with Prometheus and Grafana.

• Using Micrometer framework, Adeptia exposes the application metrics over an HTTP/s URL in the Prometheus format that can be scraped by Prometheus.
  
  Prometheus tool can be configured to pull the metrics periodically and store data. You can also configure rules in the Prometheus tool that are evaluated periodically and can send alerts to Alert Manager (in Prometheus) to send out notifications via methods such as email, Slack, etc.
• Grafana allows visualizing the data stored in Prometheus through flexible dashboards.
  You can monitor the activities including transactions, triggers, process flows, audit trail, etc. on the dashboard.

Below is the list of URLs exposed by Microservices.

• Gateway: <URL of Gateway service>/prometheus
• Portal: <URL of Portal service>/prometheus
• Event: <URL of Event service>/event/prometheus
• Runtime: <URL of Runtime service>/runtime/prometheus
• Webrunner: <URL of Webrunner service>/adeptia/prometheus

Prometheus and Grafana can be accessed via the URLs mentioned below.

• Prometheus URL
• Grafana URL