Adeptia Connect integrates EFK for logging, and Prometheus and Grafana for monitoring purposes. If you opt for EFK as a logging tool while deploying Adeptia Connect v4.0, the EFK stack is automatically deployed. In case you go for a tool other than EFK, you need to manually install and configure it. If you opt for Prometheus and Grafana as monitoring tools while deploying Adeptia Connect v4.0, you need not set up any external tool for monitoring purposes. In case you go for a tool other than Prometheus and Grafana, you need to manually install and configure it. 

Logging

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 The three components – Elastic search, Fluentd, Kibana – each working – constitute the EFK tool. Each of the components work 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 Here's how it EFK works.

• Fluentd collects the logs from Kubernetes and pushes them to into Elastic search. 
• Elastic search creates maintains the index doc for of all the logs.
• Kibana looks into the Elastic search and acts as a UI to show the logs.

...

• is the UI where you can view the logs available in Elastic search.

Monitoring

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

Prometheus collects the data information metrices from Adeptia Connect by using the URLs exposed by different Microservices and pass it on to Grafana . – a tool that shows you the detailed information and logs for various services including transactions, triggers, process flows, audit trail, etc. It helps you keep a watch on the overall health of the system. 

Here's the exposed URLs:

• dfgfdg
• dfgfdgdf

...

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

Configuring Prometheus

TBD

Configuring Grafana 

To view the metrices, you need to create a dashboard in Grafana. Before you create a dashboard, you need to configure the Prometheus data source in Grafana to dynamically display the data available in Prometheus. For detailed steps, visit the following pages.

Configuring the Prometheus data source.

Creating Grafana dashboard.

prometheus and Grafana can be accessed via the URLS mentioned below.

• xvbcvb
• cvbcvb

slide 12 -  to check pods status from a prometheus URL (valuelabs will provide URL)

Configure Grafana via a URL (valuelabs will provide URL) to provide info about Prometheus 

slide 16

Image Removed

Importing Grafana dashboard

Method 1

Method 2

Method 3

...