Using Grafana dashboard
Grafana is an open-source solution for running data analytics, reporting metrics of massive data sets and providing customizable dashboards. The tool helps to visualize metrics, time series data and application analytics.
The dashboard helps to:
Explore the data
Track user behaviour
Track application behaviour
Identify the frequency and type of errors in production or staging environments.
Grafana with Lyve Cloud analytics platform natively integrates with other services so you can securely add, query, visualize, and analyze your data across multiple accounts and regions.
Configuring Grafana service
On the left-hand menu of the Platform Dashboard, select Services and then select New Services.
In the Create a new service dialogue, complete the following configuration:
Basic Settings: Configure your service by entering the following details:
Service type: Select Grafanafrom the list.
Service name: Enter the service name. This name is listed on the Services page.
Description: Enter the description of the service.
Enabled: The check box is selected by default. Selecting the option allows you to configure the Common and Custom parameters for the service.
Common Parameters: Configure the memory and CPU resources for the service. If you do not enter any values, the platform uses the default system values.
Note
When setting the resource limits, consider that an insufficient limit might fail to execute the queries.
Memory: Provide a minimum and maximum memory based on requirements by analyzing the cluster size, resources and available memory on nodes. Trino uses memory only within the specified limit.
CPU: Provide a minimum and maximum number of CPUs based on the requirement by analyzing cluster size, resources and availability on nodes. Trino uses CPU only the specified limit.
Priority Class: By default, the priority is selected as Medium. You can change it to High or Low.
Running User: Specifies the logged-in user ID.
Custom Parameters: Configure the user and the node label key and value.
Platform data-access user: Enter the username/First Name/Last Name/Email of the user who has data access to the platform's data containers.
Node Selection: Assign a node for the services to run. The Grafana service will run only on the nodes that are defined with the labels. Select Create a new entry.
Key: Enter the key for the node label.
Value: Enter the value of the key.
Note
If there are conflicting key values, where the same key is assigned for multiple servers but it has different values, the system prompts you to delete the duplicate keys.
Select Save Service.
Understanding pre-built panels and dashboard
Grafana makes it easy to construct the right queries and customize the display properties to create your required dashboard. With multiple pre-built dashboards for various data sources, you can instantly start visualizing and analyzing your application data without having to build dashboards from scratch.
The following image shows a pre-built dashboard visualizing data for a Kubernetes cluster. Grafana provides pre-built dashboards to help you get started quickly.

Viewing Grafana dashboards
You can view and create a new dashboard for a cluster.
On the left-hand menu of the Platform Dashboard, select Clusters.
On the Clusters page select the Applications tab, and then select Status Dashboard.
Selecting Status Dashboard directs you to the Grafana dashboard of the corresponding cluster.
Monitor the cluster resource usage.
In this case, Kubernetes Resource Usage Analysis is used as an example as a cluster resource usage. However you can search for other cluster resources such as Kubernetes Custer Health, Kubernetes Cluster Status, etc.
On the Status Dashboard, select Dashboard, and then select Manage.
On the Dashboard page, select Private folder, and search Kubernetes Resource Usage Analysis.
The Kubernetes Resource Usage Analysis displays the Overall usage, Total usage, Usage by Node, Usage by Pod, etc.
You can expand the resources to view the graphical representation of the usage dashboard.
Usage Overview
Usage Overview
Pending/ Failed Pods
Pod Count
Usage - Total
Usage – By Nodes
Usage – By Pods