Monitoring service
The Monitoring service deploys the Prometheus server inside ADS to collect and store ADS cluster monitoring metrics. It also supports usage of the Grafana web application for visualization and analysis of information. This article describes steps required to add this service to an ADS cluster.
Overview
When you add the Monitoring service to an ADS cluster, node exporter is installed on all hosts. It is a monitoring agent that reads host system metrics collected by Prometheus. Prometheus also collects metrics from the ADS services (Kafka, ZooKeeper, Kafka REST Proxy, Schema-registry, ksqlDB, NiFi, MiNiFi, Kafka Connect). These metrics are available in the Prometheus format on ports and endpoints specified in service configuration settings. You can also use the Prometheus and Grafana web interfaces to view and analyze data that the monitoring service collects.
|
NOTE
|
Step 1. Add the service
-
In the ADCM interface, open the Clusters page and click your ADS cluster name. On the cluster page that opens, switch to the Services tab and click Add services.
Switch to adding services -
In the opened dialog, select the Monitoring service and click Add.
Select the serviceAs a result, the added service is displayed on the Services tab.
The result of successful adding the service to the cluster
Step 2. Add components
-
On the cluster page, open the Mapping tab to proceed to mapping service components to cluster hosts.
Switch to mapping service componentsMonitoring service components Component Description Prometheus Server
Deploys a Prometheus server that serves as a:
-
proxy channel for all collectors of metrics on a host;
-
storage for all metrics of a cluster;
-
generator of alerts based on collected metrics.
Grafana
Visualizes ADS metrics as graphs and charts organized into dashboards
Node-exporter
Exports ADS host metrics to Prometheus
-
-
Assign a host to each component of the Monitoring service — click Add hosts and select the desired host in the pop-up window.
Select a host for a componentCAUTIONIt is not recommended to install the Prometheus Server components on hosts with ADS — use separate hosts for them. Otherwise, if an ADS host fails and/or the load on it is critically high, information about the corresponding problems will not be saved. -
After the distribution of components is completed, click Save.
Save mapping of components
Step 3. Configure the service
-
Open the Services tab on the cluster page and click the Monitoring service name in the Name column.
Switch to the service configuration -
On the page that opens, fill in the service’s configuration parameters — see the Monitoring section in the ADS configuration parameters article for parameter descriptions. Fields highlighted in red are required.
Configure the Monitoring serviceAfter specifying all necessary parameters, click Save.
Step 4. Install the service
-
On the Services tab, click
for the Monitoring service in the Actions column and run the Install action.
Switch to the service installation -
Confirm the action in the opened window.
Confirm the action -
Wait until the installation is complete. Then check that the service state has changed from
createdtoinstalled.
Installation is completeTo view the service installation process and analyze errors if they occur, select Jobs in the left navigation menu and click the Install job name in the Jobs list.
Install service job page
Step 5. View results
The Monitoring service starts automatically after installation. To ensure that monitoring works correctly, check the following:
-
Metrics are collected from all hosts of your cluster, not only from the hosts where components of the monitoring service are deployed.
-
Both system and ADS service metrics are collected from the cluster hosts — see ADS monitoring metrics.
To check both these points, you can view metrics in the Prometheus format in the browser, and also use the Prometheus or Grafana web interface.
Metrics in the Prometheus format
-
In the address bar of the browser, enter the ADS cluster host address, and also specify the port and endpoint of access to the system metrics, which are defined on the configuration page of the Monitoring service in the Node exporter settings section, designed to configure access to system metrics of the ADS cluster host.
An example address for viewing ADS host metrics on a host with IP
10.92.41.147: http://10.92.41.147:11203/metrics. -
The page that opens will display monitoring metrics from the specified host of the ADS cluster in the Prometheus format.
Prometheus web interface
-
In the address bar of your browser, enter the IP address of the host where the Prometheus Server component of the Monitoring service is installed. Specify the port number, which is determined by the web.listen-address parameter in the Prometheus settings section in the Service parameters group of the Monitoring service configuration (the default port is
11200). For example: http://10.92.41.147:11200. To log into the Prometheus interface, use a username and password that are also specified in the Prometheus settings section — the Prometheus users to login/logout to Prometheus setting. -
In the Expression field, you can enter a metric and click Execute — values of this metric on all hosts of the ADS cluster will be shown in the interface.
Grafana web interface
-
In the address bar of your browser, enter an address of a host on which Grafana is deployed and add a port number — a value of the Grafana listen port parameter located in the Grafana settings section of the Monitoring service configuration (the default value is
11210). For example, http://10.92.41.147:11210. To log in, useadminas a username, and the Grafana administrator’s password parameter value (also found in the Grafana settings section of service configuration parameters) as a password. -
In the window that opens, navigate to Home → Dashboards and expand the ADS Dashboard <ADS_cluster_name> section. In this section, you can select one of available dashboards to view service or system metrics coming from your ADS cluster.
