diff options
Diffstat (limited to 'docs/node-mixin/dashboards/use.libsonnet')
-rw-r--r-- | docs/node-mixin/dashboards/use.libsonnet | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/node-mixin/dashboards/use.libsonnet b/docs/node-mixin/dashboards/use.libsonnet index 160cfd8..7499493 100644 --- a/docs/node-mixin/dashboards/use.libsonnet +++ b/docs/node-mixin/dashboards/use.libsonnet | |||
@@ -23,7 +23,8 @@ local g = import 'grafana-builder/grafana.libsonnet'; | |||
23 | { yaxes: g.yaxes({ format: 'percentunit', max: 1 }) }, | 23 | { yaxes: g.yaxes({ format: 'percentunit', max: 1 }) }, |
24 | ) | 24 | ) |
25 | .addPanel( | 25 | .addPanel( |
26 | // TODO: Is this a useful panel? | 26 | // TODO: Is this a useful panel? At least there should be some explanation how load |
27 | // average relates to the "CPU saturation" in the title. | ||
27 | g.panel('CPU Saturation (load1 per CPU)') + | 28 | g.panel('CPU Saturation (load1 per CPU)') + |
28 | g.queryPanel(||| | 29 | g.queryPanel(||| |
29 | ( | 30 | ( |
@@ -58,6 +59,8 @@ local g = import 'grafana-builder/grafana.libsonnet'; | |||
58 | g.panel('Disk IO Utilisation') + | 59 | g.panel('Disk IO Utilisation') + |
59 | // Full utilisation would be all disks on each node spending an average of | 60 | // Full utilisation would be all disks on each node spending an average of |
60 | // 1 second per second doing I/O, normalize by metric cardinality for stacked charts. | 61 | // 1 second per second doing I/O, normalize by metric cardinality for stacked charts. |
62 | // TODO: Does the partition by device make sense? Using the most utilized device per | ||
63 | // instance might make more sense. | ||
61 | g.queryPanel(||| | 64 | g.queryPanel(||| |
62 | ( | 65 | ( |
63 | instance_device:node_disk_io_time_seconds:rate1m{%(nodeExporterSelector)s} | 66 | instance_device:node_disk_io_time_seconds:rate1m{%(nodeExporterSelector)s} |
@@ -113,7 +116,7 @@ local g = import 'grafana-builder/grafana.libsonnet'; | |||
113 | .addRow( | 116 | .addRow( |
114 | g.row('Storage') | 117 | g.row('Storage') |
115 | .addPanel( | 118 | .addPanel( |
116 | g.panel('Disk Capacity') + | 119 | g.panel('Disk Space Utilisation') + |
117 | g.queryPanel(||| | 120 | g.queryPanel(||| |
118 | ( | 121 | ( |
119 | sum without (device) ( | 122 | sum without (device) ( |
@@ -145,6 +148,8 @@ local g = import 'grafana-builder/grafana.libsonnet'; | |||
145 | { yaxes: g.yaxes('percentunit') }, | 148 | { yaxes: g.yaxes('percentunit') }, |
146 | ) | 149 | ) |
147 | .addPanel( | 150 | .addPanel( |
151 | // TODO: Is this a useful panel? At least there should be some explanation how load | ||
152 | // average relates to the "CPU saturation" in the title. | ||
148 | g.panel('CPU Saturation (Load1)') + | 153 | g.panel('CPU Saturation (Load1)') + |
149 | g.queryPanel('instance:node_cpu_saturation_load1:{%(nodeExporterSelector)s, instance="$instance"}' % $._config, 'Saturation') + | 154 | g.queryPanel('instance:node_cpu_saturation_load1:{%(nodeExporterSelector)s, instance="$instance"}' % $._config, 'Saturation') + |
150 | { yaxes: g.yaxes('percentunit') }, | 155 | { yaxes: g.yaxes('percentunit') }, |