This document covers the main aspects of the Kublr Monitoring feature.
The Kublr Centralized Monitoring feature is built on top of Prometheus and Grafana. Each Kublr Platform-managed Cluster is registered as metrics source in Prometheus. Kubernetes provides cloud, hardware, OS, kubernetes, and applications metrics using Kubernetes API from each cluster respectively. Kublr manages a list of the metrics sources in the Prometheus. Grafana is integrated with the Kublr Control Plane with a single-sign on interface. A centralized monitoring component is deployed to the Kublr Platform as the helm package.
Go to the Cluster’s page and click the Add Kublr Platform button.
Select your Provider.
Fill the necessary parameters (e.g. Full Kublr Platform Credentials).
Select Instance Type for Nodes more than default, for example
t2.2xlarge for AWS or
Standard_A8_v2 for Azure.
Centralized Monitoring is always enables when creating a Platform.
Once the Platform is created, log in with Full Kublr Platform Credentials and go to the Centralized Monitoring tab.
Now you can open Grafana, Prometheus or Alert Manager. Please refer to the “Kublr General Architecture Overview” for more details about Centralized Monitoring architecture.
In some cases, self-hosted (per cluster) monitoring is required. To do that, go to the Cluster tab and click “+ Add Cluster”.
Then click “Add monitoring”
Then click Create cluster.
You can use links on the Cluster Overview page to log into Grafana, Prometheus and Alert Manager.
By default we use proxy mode, so first open “Kube Config File” and copy user and password from the Overview page.
Tip: By default, Grafana has passwords. To find them, please click the “Open Dashboard” link on the Overview page.
Then find Grafana’s pod (namespace : kube-system). Click on link and copy the user name and password.