You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/generated/metrics/metrics.yaml
+11-7Lines changed: 11 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -10553,13 +10553,13 @@ layers:
10553
10553
essential: true
10554
10554
- name: storage.wal.fsync.latency
10555
10555
exported_name: storage_wal_fsync_latency
10556
-
description: The write ahead log fsync latency
10556
+
description: The fsync latency to the Write-Ahead Log device.
10557
10557
y_axis_label: Fsync Latency
10558
10558
type: HISTOGRAM
10559
10559
unit: NANOSECONDS
10560
10560
aggregation: AVG
10561
10561
derivative: NONE
10562
-
how_to_use: If this value is greater than `100ms`, it is an indication of a disk stall. To mitigate the effects of disk stalls, consider deploying your cluster with WAL failover configured.
10562
+
how_to_use: If this value is greater than 100ms, it is an indication of a disk stall. To mitigate the effects of disk stalls, consider deploying your cluster with WAL failover configured. When WAL failover is configured, the more relevant metric is storage.wal.failover_write_and_sync.latency, as this metric reflects the fsync latency of the primary and/or the secondary WAL device.
10563
10563
essential: true
10564
10564
- name: storage.write-stalls
10565
10565
exported_name: storage_write_stalls
@@ -17311,36 +17311,38 @@ layers:
17311
17311
derivative: NON_NEGATIVE_DERIVATIVE
17312
17312
- name: storage.wal.bytes_in
17313
17313
exported_name: storage_wal_bytes_in
17314
-
description: The number of logical bytes the storage engine has written to the WAL
17314
+
description: The number of logical bytes the storage engine has written to the Write-Ahead Log.
17315
17315
y_axis_label: Events
17316
17316
type: COUNTER
17317
17317
unit: COUNT
17318
17318
aggregation: AVG
17319
17319
derivative: NON_NEGATIVE_DERIVATIVE
17320
17320
- name: storage.wal.bytes_written
17321
17321
exported_name: storage_wal_bytes_written
17322
-
description: The number of bytes the storage engine has written to the WAL
17322
+
description: The number of bytes the storage engine has written to the Write-Ahead Log.
Copy file name to clipboardExpand all lines: pkg/kv/kvserver/metrics.go
+19-13Lines changed: 19 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -2774,52 +2774,58 @@ Note that the measurement does not include the duration for replicating the eval
2774
2774
}
2775
2775
metaWALBytesWritten= metric.Metadata{
2776
2776
Name: "storage.wal.bytes_written",
2777
-
Help: "The number of bytes the storage engine has written to the WAL",
2777
+
Help: "The number of bytes the storage engine has written to the Write-Ahead Log.",
2778
2778
Measurement: "Events",
2779
2779
Unit: metric.Unit_COUNT,
2780
2780
}
2781
2781
metaWALBytesIn= metric.Metadata{
2782
2782
Name: "storage.wal.bytes_in",
2783
-
Help: "The number of logical bytes the storage engine has written to the WAL",
2783
+
Help: "The number of logical bytes the storage engine has written to the Write-Ahead Log.",
2784
2784
Measurement: "Events",
2785
2785
Unit: metric.Unit_COUNT,
2786
2786
}
2787
2787
metaStorageFsyncLatency= metric.Metadata{
2788
2788
Name: "storage.wal.fsync.latency",
2789
-
Help: "The write ahead log fsync latency",
2789
+
Help: "The fsync latency to the Write-Ahead Log device.",
2790
2790
Measurement: "Fsync Latency",
2791
2791
Unit: metric.Unit_NANOSECONDS,
2792
2792
Essential: true,
2793
2793
Category: metric.Metadata_STORAGE,
2794
-
HowToUse: "If this value is greater than `100ms`, it is an indication of a disk stall. To mitigate the effects of disk stalls, consider deploying your cluster with WAL failover configured.",
2794
+
HowToUse: "If this value is greater than 100ms, it is an indication of a disk stall. "+
2795
+
"To mitigate the effects of disk stalls, consider deploying your cluster with WAL failover configured. "+
2796
+
"When WAL failover is configured, the more relevant metric is storage.wal.failover_write_and_sync.latency, as "+
2797
+
"this metric reflects the fsync latency of the primary and/or the secondary WAL device.",
0 commit comments