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: ICINGA.md
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,18 @@
4
4
5
5
### Single / specific Plugins
6
6
7
-
By importing Baskets
7
+
#### By importing Baskets
8
+
8
9
For each check, we provide an Icinga Director Basket that contains at least the Command definition and a matching Service Template (for example, `check-plugins/cpu-usage/icingaweb2-module-director/cpu-usage.json`). Import this:
9
10
10
11
* either via the WebGUI using Icinga Director \> Configuration Baskets \> Upload, select the latest entry in the Snapshots tab and restore it
11
12
* or via `icingacli director basket restore < cpu-usage.json -v`
12
13
13
14
Now use the new commands within Service Templates, Service Sets and/or a Single Services.
14
15
15
-
By defining them manually
16
+
17
+
#### By defining them manually
18
+
16
19
If you want to define plugins manually, this is how to do it (example).
17
20
18
21
Create a command for "cpu-usage" in Icinga Director \> Commands \> Commands:
@@ -40,6 +43,7 @@ Tab "Fields":
40
43
* Label "CPU Usage: Critical", Field name "cpu_usage_critical", Mandatory "n"
41
44
* Label "CPU Usage: Warning", Field name "cpu_usage_warning", Mandatory "n"
42
45
46
+
43
47
### All Plugins (Linuxfabrik Icinga Director Configuration)
44
48
45
49
To use the Linuxfabrik Icinga Director configuration, including host templates, notification templates and predefined service sets, you need to *generate* a single Icinga Director basket file containing the baskets for each check plus [all-the-rest.json](https://github.com/Linuxfabrik/monitoring-plugins/blob/main/assets/icingaweb2-module-director/all-the-rest.json). Use [tools/basket-join](https://github.com/Linuxfabrik/monitoring-plugins/blob/main/tools/basket-join) to do this.
@@ -48,28 +52,31 @@ Create the Icinga Director Basket JSON file:
48
52
49
53
* If you are using our [Fork of the Icinga Director](https://github.com/Linuxfabrik/icingaweb2-module-director), which introduced uuids, you can use the following command:
50
54
51
-
```bash
52
-
./tools/basket-join
53
-
```
55
+
```bash
56
+
./tools/basket-join
57
+
```
54
58
55
-
* If you are NOT using our [Fork of the Icinga Director](https://github.com/Linuxfabrik/icingaweb2-module-director), create a basket without uuids:
59
+
* If you are NOT using our Fork of the Icinga Director, create a basket without uuids:
If you did not name your master zone `master` during the initial `icinga2 node wizard`, find and replace `"zone": "master"` with `"zone": "your-master-zone-name"` in the `icingaweb2-module-director-basket.json` file.
61
69
62
70
Import the resulting `icingaweb2-module-director-basket.json`:
63
71
64
72
* either via the WebGUI using *Icinga Director \> Configuration Baskets \> Upload*, select the latest entry in the Snapshots tab and restore it
65
-
* or via `icingacli director basket restore < icingaweb2-module-director-basket.json -v`.
73
+
* or via `icingacli director basket restore < icingaweb2-module-director-basket.json -v` (preferred).
66
74
67
75
If you get the error message `File 'icingaweb2-module-director-basket.json' exeeds the defined ini size.`, adjust your PHP and/or MariaDB/MySQL settings (as described in [Cant Upload Director Basket](https://github.com/Icinga/icingaweb2-module-director/issues/2458)):
68
76
69
77
* PHP: increase `upload_max_filesize` and `post_max_size` (if you use PHP-FPM, don't forget to restart this service).
70
78
* MariaDB/MySQL: increase `max_allowed_packet`.
71
79
72
-
If you did not name your master zone `master` during the initial `icinga2 node wizard`, find and replace `"zone": "master"` with `"zone": "your-master-zone-name"` in the `icingaweb2-module-director-basket.json` file.
73
80
74
81
## Linuxfabrik's Icinga Director Concept
75
82
@@ -79,6 +86,7 @@ In general, all of our services are in a service set, which is then applied to a
79
86
80
87
For some services it does not make sense to create a set, for example when monitoring an external website using `tpl-service-url`. In this case you can create a single service on that host.
81
88
89
+
82
90
### Criticality
83
91
84
92
To manage notifications we use a custom variable called `criticality`. This variable is present on both services and hosts and is used to determine if and during what time period a notification is sent.
0 commit comments