mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
* fix a few bare URLs * make mdl happy * make Weathermap.md as mdl happy as possible * make Varnish.md as mdl happy as possible * make Two-Factor-Auth.md mdl happy * touch one header for Syslog.md, but little can be done about the rest * make Sub-Directory.md as mdl happy as possible * make SNMP-Trap-Handler.md lint happy * make SNMP-Proxy.md mdl happy * make Smokeping.md as mdl happy as possible * make Services.md mdl happy * make RRDTune.md mdl happy * cleanup RRDCached.md as much as possible * make RRDCached-Security.md mdl happy * make Rancid.md as mdl happy as possible * make Proxmox.md mdl happy * make Plugin-System.md as mdl happy as possible * make PeeringDB.md mdl happy * make Oxidized.md more lint happy * make Network-Map.md mdl happy * make MIB-based-polling.md as mdl happy as possible * make Metric-Storage.md mdl happy * make IRC-Bot.md as mdl happy as possible * make IRC-Bot-Extensions.md as mdl happy as possible * make * make Graylog.md mdl happy * make Gateone.md mdl happy * make Fast-Ping-Check.md mdl happy * make Distributed-Poller.md as mdl happy as possible * make Dispatcher-Service.md as mdl happy as possible * make Device-Groups.md mdl happy * make Dell-OpenManage.md mdl happy * make Dashboard.md mdl happy * make Customizing-the-Web-UI.md as mdl happy as possible * make Component.md mdl happy * make Billing-Module.md mdl happy * make Auto-Discovery.md mostly mdl happy * make Authentication.md as mdl happy as possible * tidy up a few lines in Applications.md * make Agent-Setup.md as mdl happy as possible * make metrics/OpenTSDB.md mdl happy * spelling fix
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
source: Extensions/Device-Groups.md
|
|
path: blob/master/doc/
|
|
|
|
LibreNMS supports grouping your devices together in much the same way
|
|
as you can configure alerts. This document will hopefully help you get
|
|
started.
|
|
|
|
# Dynamic Groups
|
|
|
|
## Rule Editor
|
|
|
|
The rule is based on the MySQL structure your data is in. Such as __tablename.columnname__.
|
|
If you already know the entity you want, you can browse around inside
|
|
MySQL using `show tables` and `desc <tablename>`.
|
|
|
|
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`.
|
|
|
|
If you want to group them by device type, you would add a rule for
|
|
routers of `devices.hostname` endswith `rtr.example.com`.
|
|
|
|
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)
|
|
|
|
# Static Groups
|
|
|
|
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.
|
|
|
|

|
|
|
|
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
|
|
`Overview -> Alerts -> Rule Mapping`.
|