Merge branch 'master' into issue-1650

doc/Extensions/Alerting.md

@@ -81,6 +81,12 @@ Alert when:
 - Any port changes: `%ports.ifOperStatus != 'up'`
 - Root-directory gets too full: `%storage.storage_descr = '/' && %storage.storage_perc >= '75'`
 - Any storage gets fuller than the 'warning': `%storage.storage_perc >= %storage_perc_warn`
+- If device is a server and the used storage is above the warning level, but ignore /boot partitions: `%storage.storage_perc > %storage.storage_perc_warn && %devices.type = "server" && %storage.storage_descr !~ "/boot"`
+- VMware LAG is not using "Source ip address hash" load balancing: `%devices.os = "vmware" && %ports.ifType = "ieee8023adLag" && %ports.ifDescr !~ "Link Aggregation @, load balancing algorithm: Source ip address hash"`
+- Syslog, authentication failure during the last 5m: `%syslog.timestamp >= %macros.past_5m && %syslog.msg ~ "@authentication failure@"`
+- High memory usage: `%macros.device_up = "1" && %mempools.mempool_perc >= "90" && %mempools.mempool_descr = "Virtual@"`
+- High CPU usage(per core usage, not overall): `%macros.device_up = "1" && %processors.processor_usage >= "90"`
+- High port usage, where description is not client & ifType is not softwareLoopback: `%macros.port_usage_perc >= "80" && %port.port_descr_type != "client" && %ports.ifType != "softwareLoopback"`
 
 # <a name="templates">Templates</a>
 

doc/Extensions/MIB-based-polling.md

@@ -69,8 +69,9 @@ The components involved in MIB-based polling are:
 
   - During discovery, relevant MIBs are parsed using `snmptranslate`, and the
     data returned is used to populate a database which guides the poller in
-    what to store.  At the moment, only OIDs with Unsigned32 and Counter64
-    data types are parsed.
+    what to store.  At the moment, only OIDs of INTEGER, Integer32, Gauge32,
+    Unsigned32, Counter32, and Counter64 data types are parsed, and negative
+    values are untested.
 
   - Devices may be excluded from MIB polling by changing the setting in the
     device edit screen:

doc/Extensions/Oxidized.md

@@ -31,14 +31,6 @@ You can set a default group that devices will fall back to with:
 $config['oxidized']['default_group'] = 'default';
 ```
 
-To return a group to Oxidized you can do this by matching a regex for either hostname or location. The order is hostname is matched first, if nothing is found then location is attempted. 
-The first match found will be used. To match on the device hostnames that contain 'lon-sw' or if the location contains 'London' then you would place the following within config.php:
-
-```php
-$config['oxidized']['group']['hostname'][] = array('regex' => '/^lon-sw/', 'group' => 'london-switches');
-$config['oxidized']['group']['location'][] = array('regex' => '/london/', 'group' => 'london-switches');
-```
-
 ### Feeding Oxidized
 
 Oxidized has support for feeding devices into it via an API call, support for Oxidized has been added to the LibreNMS API. A sample config for Oxidized is provided below.
@@ -56,10 +48,40 @@ You will need to configure default credentials for your devices, LibreNMS doesn'
           map:
             name: hostname
             model: os
+            group: group
           headers:
             X-Auth-Token: '01582bf94c03104ecb7953dsadsadwed'
 ```
 
+LibreNMS is able to reload the Oxidized list of nodes, each time a device is added to LibreNMS.
+To do so, edit the option in Global Settings>External Settings>Oxidized Integration or add the following to your config.php.
+
+```php
+$config['oxidized']['reload_nodes'] = TRUE;
+
+```
+
+### Using Groups
+
+To return a group to Oxidized you can do this by matching a regex for either hostname or location. The order is hostname is matched first, if nothing is found then location is attempted.
+The first match found will be used. To match on the device hostnames that contain 'lon-sw' or if the location contains 'London' then you would place the following within config.php:
+
+```php
+$config['oxidized']['group']['hostname'][] = array('regex' => '/^lon-sw/', 'group' => 'london-switches');
+$config['oxidized']['group']['location'][] = array('regex' => '/london/', 'group' => 'london-switches');
+```
+
+If you need to, you can specify credentials for groups by using the following in your Oxidized config:
+
+```bash
+groups:
+  <groupname>:
+    username: <user>
+    password: <password>
+```
+
+### Miscellaneous
+
 If you have devices which you do not wish to appear in Oxidized then you can edit those devices in Device -> Edit -> Misc and enable "Exclude from Oxidized?"
 
 It's also possible to exclude certain device types and OS' from being output via the API. This is currently only possible via config.php:

doc/Support/Configuration.md

@@ -488,6 +488,7 @@ This array can be used to filter out syslog messages that you don't want to be s
 ```php
 $config['enable_libvirt'] = 1;
 $config['libvirt_protocols']    = array("qemu+ssh","xen+ssh");
+$config['libvirt_username'] = 'root';
 ```
 Enable this to switch on support for libvirt along with `libvirt_protocols`
 to indicate how you connect to libvirt.  You also need to:

doc/Support/Poller Support.md

@@ -39,7 +39,6 @@ disable it for one device then you can do this within the WebUI -> Settings -> M
 
 ```php
 $config['poller_modules']['unix-agent']                   = 0;
-$config['poller_modules']['system']                       = 1;
 $config['poller_modules']['os']                           = 1;
 $config['poller_modules']['ipmi']                         = 1;
 $config['poller_modules']['sensors']                      = 1;