2021-07-09 05:10:05 +08:00
|
|
|
# Grouping Devices
|
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
LibreNMS supports grouping your devices together in much the same way
|
|
|
|
as you can configure alerts. This document will hopefully help you get
|
|
|
|
started.
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2021-07-09 05:10:05 +08:00
|
|
|
## Dynamic Groups
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2021-07-09 05:10:05 +08:00
|
|
|
### Rule Editor
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-06-19 16:01:53 -05:00
|
|
|
The rule is based on the MySQL structure your data is in. Such as __tablename.columnname__.
|
2019-09-09 05:48:35 -05:00
|
|
|
If you already know the entity you want, you can browse around inside
|
|
|
|
MySQL using `show tables` and `desc <tablename>`.
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
As a working example and a common question, let's assume you want to
|
|
|
|
group devices by hostname. If your hostname format is
|
|
|
|
dcX.[devicetype].example.com. You would use the field
|
|
|
|
`devices.hostname`.
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
If you want to group them by device type, you would add a rule for
|
|
|
|
routers of `devices.hostname` endswith `rtr.example.com`.
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
If you want to group them by DC, you could use the rule
|
|
|
|
`devices.hostname` regex `dc1\..*\.example\.com` (Don't forget to
|
|
|
|
escape periods in the regex)
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2021-07-09 05:10:05 +08:00
|
|
|
## Static Groups
|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
You can create static groups (and convert dynamic groups to static) to
|
|
|
|
put specific devices in a group. Just select static as the type and
|
|
|
|
select the devices you want in the group.
|
2017-10-02 21:36:22 +01:00
|
|
|
|
|
|
|

|
2015-08-27 20:29:16 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
You can now select this group from the Devices -> All Devices link in
|
|
|
|
the navigation at the top. You can also use the group to map alert
|
|
|
|
rules to by creating an alert mapping
|
2016-08-26 00:40:11 +01:00
|
|
|
`Overview -> Alerts -> Rule Mapping`.
|