Grafana Monitoring Dashboards

Grafana dashboard: Prometheus-powered efficient monitoring that provides significant insights and visualizations for improved operational visibility and analysis.

  1. HOME PAGE

Grafana's homepage presents an assortment of dashboards, each of which is accessible by easy button-like pictures. These photos are housed on an S3 bucket, and users are seamlessly forwarded to their respective dashboards upon clicking, streamlining navigation and improving user experience within the Grafana monitoring platform.

  1. SERVER

The Server Dashboard displays essential information such as CPU and memory use, disk performance, and network traffic statistics. Users may quickly monitor and analyze these critical parameters, allowing for more effective resource management and server performance optimization.

  • The CPU and Memory usage Grafana dashboard panels display system performance in real time. Monitoring these critical resources is critical for improving efficiency, finding bottlenecks, and assuring application smooth functioning, eventually improving overall system reliability and user happiness.

  • The use of the file system and inodes usage Grafana dashboard panel gives vital information about storage consumption and availability. Monitoring these indicators is critical for proactive resource management, preventing disk space concerns, guaranteeing system stability, and ensuring that applications and services run smoothly.

  • The average load Grafana dashboard panel depicts system load over time. Monitoring average load is critical for determining system health, optimizing resource allocation, and assuring peak performance. It enables administrators to make informed decisions in order to preserve system efficiency and responsiveness under various workload conditions.

  • CPU and Memory usage of the pods - The Grafana dashboard panel provides vital information into Kubernetes pod resource use. Monitoring these pods is critical for resource management efficiency, maintaining optimal pod performance, and scaling resources as needed to maintain a high-performing and dependable application infrastructure.

  • The Grafana dashboard panel "Pods Network IO Pressure" displays network input/output pressure within Kubernetes pods. For efficient network resource management, performance optimization, and smooth communication across pods—improving overall application dependability and user experience—this statistic must be closely monitored.

  1. CLUSTER -

Essential data like cluster CPU Request, Limit, and Usage as well as memory Request, Limit, and Usage are prominently presented in the cluster dashboard. For effective resource management and capacity planning, monitoring these KPIs is essential, assuring the best performance and stability for the entire Kubernetes cluster.

  • The Cluster Dashboard's overall state offers information on container status inside the Kubernetes cluster. This contains information on containers that are running, terminated, waiting, and restarted (for the last 30 minutes), which aids in monitoring container health and successfully addressing possible issues.

  • The dashboard's "Cluster Health" section displays critical information about cluster CPU and RAM consumption, as well as their respective request and limit levels. This complete view enables effective resource use monitoring and supports in capacity planning and performance optimization for the Kubernetes cluster.

  • The "Cluster Health" panel in this part displays the CPU and RAM use in the Kubernetes cluster. This information is essential for monitoring overall cluster performance and ensuring effective resource allocation and management.

  1. MINER

Miner dashboard displays statistics on CPU and memory utilization for miners and the databases (redis & redis_txns) they are connected to. For monitoring performance, maximizing resource allocation, and assuring effective operations of the providers and databases within the Kubernetes cluster, this visibility is crucial.

  • The dashboard panel shows Miner total CPU and memory utilization for the corresponding miners in this area. Understanding and controlling the overall resource usage of the miners within the Kubernetes cluster depends on this information.

  • The dashboard offers insights into the CPU and memory utilization of specific miner in this section. For monitoring and optimizing resource usage for each distinct provider within the Kubernetes cluster, this fine-grained data is crucial.

  • The dashboard provides a thorough view of specific Redis database in this part, displaying their corresponding CPU and memory utilization. This data is essential for tracking database performance, spotting possible bottlenecks, and allocating resources efficiently.

The dashboard provides a thorough view of specific Redis Txns database in this part, displaying their corresponding CPU and memory utilization. This data is essential for tracking database performance, spotting possible bottlenecks, and allocating resources efficiently.

  • The dashboard displays the precise CPU and memory use limits for miner & it's database in this area. This level of specificity is necessary for accurate resource management and capacity planning for the miner within the Kubernetes cluster.

  1. SHARDER

In Sharder Dashboard, displays statistics on CPU and memory utilization for sharders and the Postgres database they are connected to. For monitoring performance, maximizing resource allocation, and assuring effective operations of the sharders and database within the Kubernetes cluster, this visibility is crucial.

  • The dashboard panel shows Sharder total CPU and memory utilization for the corresponding sharders in this area. Understanding and controlling the overall resource usage of the miners within the Kubernetes cluster depends on this information.

  • The dashboard in this area provides information about each sharder's disk utilization. Understanding disk utilization is critical for monitoring storage resources, optimizing performance, and ensuring the providers in the Kubernetes cluster operate efficiently.

    • disk usage will grow because new generated blocks are stored on server storage every second.

  • The dashboard offers insights into the CPU and memory utilization of specific sharder in this section. For monitoring and optimizing resource usage for each distinct provider within the Kubernetes cluster, this fine-grained data is crucial.

  • The dashboard provides a thorough view of specific Postgres database in this part, displaying their corresponding CPU and memory utilization. This data is essential for tracking database performance, spotting possible bottlenecks, and allocating resources efficiently.

  • The dashboard displays the precise CPU and memory use limits for sharder & it's database in this area. This level of specificity is necessary for accurate resource management and capacity planning for the miner within the Kubernetes cluster.

  1. BLOBBER

In Blobber Dashboard, displays statistics on CPU and memory utilization for blobbers and the Postgres database they are connected to. For monitoring performance, maximizing resource allocation, and assuring effective operations of the blobbers and Postgres database within the Kubernetes cluster, this visibility is crucial.

  • The dashboard panel shows Blobber total CPU and memory utilization for the corresponding blobbers in this area. Understanding and controlling the overall resource usage of the miners within the Kubernetes cluster depends on this information.

  • The dashboard offers insights into the CPU and memory utilization of specific blobber in this section. For monitoring and optimizing resource usage for each distinct provider within the Kubernetes cluster, this fine-grained data is crucial.

  • The dashboard offers insights into the CPU and memory utilization of specific validator in this section. For monitoring and optimizing resource usage for each distinct provider within the Kubernetes cluster, this fine-grained data is crucial.

  • The dashboard provides a thorough view of specific Postgres database in this part, displaying their corresponding CPU and memory utilization. This data is essential for tracking database performance, spotting possible bottlenecks, and allocating resources efficiently.

  • The dashboard displays the precise CPU and memory use limits for blobber & it's database in this area. This level of specificity is necessary for accurate resource management and capacity planning for the miner within the Kubernetes cluster.

  1. MISCELLANEOUS PODS

The Miscellaneous dashboard provides metrics linked to Rancher and Ingress in this section, highlighting their respective CPU and memory utilization. This visibility is crucial for monitoring and optimizing Rancher and Ingress performance within the Kubernetes cluster.

  • The dashboard panel shows total CPU and memory utilization for the corresponding Rancher, Ingress, Grafana and Cert Manager in this area. Understanding and controlling the overall resource usage of the miners within the Kubernetes cluster depends on this information.

  • In this part, the dashboard displays Rancher-specific metrics, such as CPU and memory utilization. These metrics must be monitored in order to optimize Rancher's performance and ensure optimal resource allocation inside the Kubernetes cluster.

  • The dashboard displays Grafana metrics in this section, providing insight into its CPU and memory utilization. These metrics must be monitored in order to optimize Grafana's performance and ensure effective resource consumption inside the Kubernetes cluster.

  • The dashboard displays stats for Cert Manager in this section, providing insight into its CPU and memory consumption. These metrics must be monitored in order to optimize Cert Manager's performance and ensure optimal resource allocation inside the Kubernetes cluster.

  • The dashboard displays metrics for the Ingress Controller in this section, offering a clear view of its CPU and memory consumption. Monitoring these metrics is critical for enhancing the performance of the Ingress Controller and ensuring optimal resource allocation within the Kubernetes cluster.

Refer following doc -

Last updated