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: CONTRIBUTING.rst
+2-46Lines changed: 2 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Checklist:
43
43
* A nice 16x16 transparent PNG icon, for example based on https://simpleicons.org or font-awesome (not in Git, will be put for download on https://download.linuxfabrik.ch).
44
44
* README file explaining "How?" and Why?"
45
45
* optional: ``unit-test/run`` - the unittest file (see `Unit Tests <#unit-tests>`_)
46
-
* optional: Grafana panel (see :doc:`GRAFANA`) and Icinga Web 2 Grafana Module .ini file
46
+
* optional: Grafana dashboard (see :doc:`GRAFANA`) and Icinga Web 2 Grafana Module .ini file, if you also define a Service Set (you need a consistent Service Name to rely on)
47
47
* optional: Icinga Director Basket Config
48
48
* optional: sudoers file (see `sudoers File <#sudoers-file>`_)
49
49
@@ -454,51 +454,7 @@ If the plugin requires ``sudo``-permissions to run, please add the plugin to the
454
454
Grafana Dashboards
455
455
------------------
456
456
457
-
Each Grafana panel should be meaningful, especially when comparing it to other related panels (eg memory usage and CPU usage). When sensible, there should be an additional panel with min, max, mean and last columns. This can be achieved my setting the visualization to table and using the transform > reduce functions. This is preferred to using the legend options, because they change the width of the graph, making it harder to correlate events across panels. Unfortunately, it is currently impossible to set the unit per row, so you need to make on additional panel for each unit.
458
-
459
-
When modifying existing panels or creating new panels, always work with the 'all-panel' dashboard (from ``assets/grafana/``). The title of the panels should be capitalized, the metrics should be lowercase. Be sure to create a new row named after the plugin. This field will be used for the automatic splitting into smaller dashboards later on. Therefore, the name has to match the folder/plugin name (spaces will be replaced with ``-``, ``/`` will be ignored. eg ``Network I/O`` will become ``network-io``).
460
-
461
-
As there are two options to import the Grafana dashboards (either importing via the WebGUI or provisioning, see the README for details), the Grafana dashboard also need to be exported twice.
462
-
463
-
Always make sure that there is no sensitive data in the export (eg. hostnames).
464
-
465
-
466
-
Exporting for later import via the WebGUI
467
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
468
-
469
-
* Make sure all rows are collapsed
470
-
* Share dashboard (Icon right of the dashboard title)
471
-
* Export
472
-
* Export for sharing externally: yes
473
-
* Save to file: all-panels-external.json
474
-
475
-
Afterwards generate the dashboards for each plugin using the
Make sure to adjust the generated ini file if necessary.
457
+
The title of the dashboard should be capitalized, the name has to match the folder/plugin name (spaces will be replaced with ``-``, ``/`` will be ignored. eg ``Network I/O`` will become ``network-io``). Each Grafana panel should be meaningful, especially when comparing it to other related panels (eg memory usage and CPU usage).
0 commit comments