Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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 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. The three components – Elastic search, Fluentd, Kibana – constitute the EFK tool. Each of the components work in tandem to serve a common purpose of working with and viewing the logs. Here's how EFK works.

  • Fluentd collects the logs from Kubernetes and pushes them into Elastic search. 
  • Elastic search maintains the index of all the logs.
  • Kibana is the UI where you can view the logs available in Elastic search.


  • You can also opt to use another third party tool for logging purposes. In this case, refer to this section to know what you need to do to configure the third party tool.

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

The metrices exposed by Adeptia Connect Microservices are in Prometheus supported format only.

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.

You can also opt to use another third party tool for monitoring purposes. In this case, refer to this section to know what you need to do to configure the third party tool.
  • No labels