mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
1a60c44eb0
* Device Groups rewrite Updated web ui Static or dynamic groups allowed Alert rule query builder Translation support Permissions support * cleanup, make relationship save, and validate it * builder WIP * rules builder and rules saving/loading * Parse query builder to Laravel Fluent query * Upgrade existing groups when editing. Properly update only dynamic groups when polling. * remove unused old code Update API and other places to use Eloquent * debug output in poller restored * Fix up some things creating static improved validation fix js error on creation Fix static groups in polling * hide pattern for static group * Implement authorization Use in the menu too * update schema * fix rollback * Don't abort on invalid queries * fixes to query builder * add test data, looks like macros aren't handled (omitted them because groups don't use them generally) * Add macro support for QueryBuilderFluentParser * add test for macro that accepts value * More space in forms Retain rules when converted to static no duplicate names allowed * Better error feedback Update related devices on save * Add button icon * format * update docs * fix tests * Fix some QueryBuilderFluentParser issues with OR updated/more test data * Show device groups runtime fix querybuilder.json format * Store table joins in the rules to minimize polling time Update group joins in daily.sh (and when they are saved) * Update daily.php * Add units to time
29 lines
1.4 KiB
Markdown
29 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`.
|