Skip to content

Commit

Permalink
feat: Add description to workload counters
Browse files Browse the repository at this point in the history
  • Loading branch information
@rahulguptajss
rahulguptajss committed Apr 21, 2023
1 parent fccf240 commit 87dfed4
Show file tree
Hide file tree
Showing 2 changed files with 64 additions and 53 deletions.
60 changes: 30 additions & 30 deletions grafana/dashboards/cmode/volume.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@
"gnetId": null,
"graphTooltip": 1,
"id": null,
"iteration": 1678952925478,
"iteration": 1682091259711,
"links": [
{
"asDropdown": true,
Expand Down Expand Up @@ -2877,6 +2877,8 @@
}
},
"mappings": [],
"max": 1,
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
Expand All @@ -2890,9 +2892,7 @@
}
]
},
"unit": "percentunit",
"min": 0,
"max": 1
"unit": "percentunit"
},
"overrides": []
},
Expand Down Expand Up @@ -2966,7 +2966,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the latency or delay associated with network operations. This includes latency introduced by network components such as switches, routers, and network adapters, as well as other factors such as congestion and packet loss.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3056,7 +3056,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the latency or delay associated with quality of service (QoS) operations when limiting the amount of input/output (I/O) operations that can be processed by a storage system.\n\nONTAP uses QoS to ensure that different workloads and applications receive the appropriate level of performance and resources. When a QoS policy is in effect and the storage system reaches its I/O limit, the DELAY_CENTER_QOS_LIMIT latency is the delay incurred by the storage system when it is unable to process any additional I/O operations.\n\nThe DELAY_CENTER_QOS_LIMIT latency is essentially the time it takes for the storage system to process the queued I/O operations once the I/O limit has been lifted. This latency can vary depending on the workload and the resources available to the storage system.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3147,7 +3147,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of delay or latency that can occur when the storage system enforces a minimum throughput or bandwidth limit for certain workloads or applications using the Quality of Service (QoS) feature.\n\nQuality of Service (QoS) is a feature in ONTAP that enables administrators to define and enforce policies for data storage operations. The DELAY_CENTER_QOS_MIN_THROUGHPUT latency is related to the enforcement of the minimum throughput policy. This helps to prevent these workloads or applications from being starved of resources and ensures that they can meet their performance requirements.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3238,7 +3238,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the latency or delay associated with interconnect traffic between the nodes in a cluster.\n\nWhen ONTAP nodes communicate with each other, they use a high-speed interconnect that allows them to share data and metadata. The DELAY_CENTER_CLUSTER_INTERCONNECT latency is the time it takes for a message or packet to travel between nodes over this interconnect.\n\nThe latency can be affected by several factors, including the type and speed of the interconnect, the distance between the nodes, and the amount of traffic on the interconnect. A high DELAY_CENTER_CLUSTER_INTERCONNECT latency can lead to slow communication between nodes, which can impact the performance and availability of the cluster.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3328,7 +3328,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of time it takes for a given dblade (disk blade) to process a request. A dblade is a hardware component that is used to interface with the physical disks in a NetApp storage system.\n\nThe CPU_dblade latency is the time it takes for the dblade to receive a request from the storage controller, process the request, and send a response back to the controller. This latency can be impacted by various factors, such as the size of the request, the amount of disk I/O being processed, and the workload on the dblade itself.\n",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3418,7 +3418,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of delay or latency that can occur when the WAFL (Write Anywhere File Layout) file system suspends operations related to checkpointing in order to prioritize a certain operation.\n\nThe WAFL suspension control point is a mechanism used by ONTAP to temporarily stop the processing of data writes in order to ensure data consistency in the event of a system failure or outage. When the suspension control point is activated, any pending data writes are held in a buffer until the system resumes normal operation.\n\nThe DELAY_CENTER_WAFL_SUSP_CP performance counter measures the latency, or delay, that occurs when the suspension control point is activated. Specifically, it measures the time between when the suspension control point is triggered and when data writes are resumed.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3509,7 +3509,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of delay or latency that can occur when the WAFL (Write Anywhere File Layout) file system suspends other operations to prioritize a certain operation.\n\nThe WAFL file system in ONTAP is designed to optimize the way data is written to disk and improve the overall performance and efficiency of the storage system. The DELAY_CENTER_WAFL_SUSP_OTHER latency can be caused by a variety of factors, such as background disk maintenance activities or other system-level events that require suspending WAFL operations temporarily. The latency associated with DELAY_CENTER_WAFL_SUSP_OTHER is dependent on the specific cause of the suspension and the resources available to the storage system.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3595,12 +3595,12 @@
],
"timeFrom": null,
"timeShift": null,
"title": "Top $TopResources Volumes by Latency from Suspend",
"title": "Top $TopResources Volumes by Latency from WAFL Suspend",
"type": "timeseries"
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the latency or delay associated with I/O operations to cloud storage services such as Amazon S3, Azure Blob Storage, or Google Cloud Storage.\n\nWhen ONTAP systems use cloud storage services, they send I/O requests over the internet to the cloud storage provider's servers. The DELAY_CENTER_CLOUD_IO latency is the time it takes for these I/O requests to be transmitted over the internet and for the cloud storage provider to process the request and return the result to ONTAP.\n\nThe latency can be affected by several factors, including the distance between the ONTAP system and the cloud storage provider's servers, the speed and quality of the internet connection, and the load on the cloud storage provider's servers.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3691,7 +3691,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of time it takes for a given nblade (network blade) to process a request. An nblade is a network interface card (NIC) that is used to handle network traffic in a NetApp storage system.\n\nThe CPU_nblade latency is the time it takes for the nblade to receive a request from the network, process the request, and send a response back to the requester. This latency can be impacted by various factors, such as the size of the request, the amount of network traffic being processed, and the workload on the nblade itself.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3781,7 +3781,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the amount of delay or latency that can occur when data is being transferred from the NVRAM (non-volatile random-access memory) to the hard disk drives in a storage system.\n\nWhen data is written to a NetApp storage system, it is first written to the NVRAM, which acts as a buffer. This allows the system to acknowledge the write operation as complete before it has been fully committed to the disk drives. However, if there is a delay in transferring data from the NVRAM to the disk drives, there can be a risk of data loss in the event of a system failure or power loss.\n\nDELAY_CENTER_NVLOG_TRANSFER helps to address this risk by providing a buffer for write operations, known as the delay center, which optimizes the transfer of data from the NVRAM to the disk drives. The delay center adjusts the rate at which data is transferred based on the performance of the storage system and helps to ensure that data is transferred in a consistent and efficient manner, which reduces the risk of data loss and improves the overall performance and reliability of the storage system.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -3871,7 +3871,7 @@
},
{
"datasource": "${DS_PROMETHEUS}",
"description": "",
"description": "This latency refers to the latency or delay associated with input/output (I/O) operations to and from disk. This delay is caused by a number of factors, such as disk seek times, rotational latency, and data transfer rates.\n\nWhen an application or user sends a read or write request to the storage system, the request is handled by the storage controller and then sent to the appropriate disk or disks. The DELAY_CENTER_DISK_IO latency is the time it takes for the disk to complete the I/O operation and return the requested data to the storage controller. This latency can be impacted by factors such as the speed and type of disk being used, the size of the data being read or written, and the workload on the disk itself.",
"fieldConfig": {
"defaults": {
"color": {
Expand Down Expand Up @@ -4010,6 +4010,7 @@
"mode": "off"
}
},
"decimals": 2,
"mappings": [],
"thresholds": {
"mode": "absolute",
Expand All @@ -4020,8 +4021,7 @@
}
]
},
"unit": "bytes",
"decimals": 2
"unit": "bytes"
},
"overrides": []
},
Expand Down Expand Up @@ -4124,6 +4124,8 @@
}
},
"mappings": [],
"max": 100,
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
Expand All @@ -4137,9 +4139,7 @@
}
]
},
"unit": "percent",
"min": 0,
"max": 100
"unit": "percent"
},
"overrides": []
},
Expand Down Expand Up @@ -4233,6 +4233,7 @@
"mode": "off"
}
},
"decimals": 2,
"mappings": [],
"thresholds": {
"mode": "absolute",
Expand All @@ -4247,8 +4248,7 @@
}
]
},
"unit": "bytes",
"decimals": 2
"unit": "bytes"
},
"overrides": []
},
Expand Down Expand Up @@ -4351,6 +4351,8 @@
}
},
"mappings": [],
"max": 100,
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
Expand All @@ -4364,9 +4366,7 @@
}
]
},
"unit": "percent",
"min": 0,
"max": 100
"unit": "percent"
},
"overrides": []
},
Expand Down Expand Up @@ -5121,6 +5121,8 @@
}
},
"mappings": [],
"max": 100,
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
Expand All @@ -5134,9 +5136,7 @@
}
]
},
"unit": "percent",
"min": 0,
"max": 100
"unit": "percent"
},
"overrides": []
},
Expand Down Expand Up @@ -6254,5 +6254,5 @@
"timezone": "",
"title": "ONTAP: Volume",
"uid": "",
"version": 9
"version": 10
}
Loading

0 comments on commit 87dfed4

Please sign in to comment.