mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
docs: Updated alerting docs / formatting (#7185)
* Ignore docs/ * Fix indenentation YAML's pretty strict * Remove static anchor names Markdown does this automatically for us * Tabelize entities * Remove tildes They don't do anything
This commit is contained in:
Bennett Blodinger
committed by
Neil Lathwood
Neil Lathwood
parent
f37f3ddff6
commit
31993387e4
4
.gitignore
vendored
4
.gitignore
vendored
@@ -29,4 +29,8 @@ rrd
|
||||
!/lib/yaml
|
||||
/vendor
|
||||
composer.phar
|
||||
|
||||
# Docs #
|
||||
########
|
||||
out
|
||||
librenms_theme
|
||||
|
||||
@@ -1,62 +0,0 @@
|
||||
source: Alerting/Alerting.md
|
||||
Table of Content:
|
||||
|
||||
- [About](#about)
|
||||
- [Rules](Rules.md)
|
||||
- [Syntax](Rules.md#rules-syntax)
|
||||
- [Options](Rules.md#extra)
|
||||
- [Examples](Rules.md#rules-examples)
|
||||
- [Procedure](Rules.md#rules-procedure)
|
||||
- [Templates](Templates.md)
|
||||
- [Syntax](Templates.md#templates-syntax)
|
||||
- [Testing](Templates.md#templates-testing)
|
||||
- [Examples](Templates.md#templates-examples)
|
||||
- [Included](Templates.md#templates-included)
|
||||
- [Transports](Transports.md)
|
||||
- [E-Mail](Transports.md#transports-email)
|
||||
- [API](Transports.md#transports-api)
|
||||
- [Nagios-Compatible](Transports.md#transports-nagios)
|
||||
- [IRC](Transports.md#transports-irc)
|
||||
- [Slack](Transports.md#transports-slack)
|
||||
- [Rocket.chat](Transports.md#transports-rocket)
|
||||
- [HipChat](Transports.md#transports-hipchat)
|
||||
- [PagerDuty](Transports.md#transports-pagerduty)
|
||||
- [Pushover](Transports.md#transports-pushover)
|
||||
- [Boxcar](#transports-boxcar)
|
||||
- [Telegram](Transports.md#transports-telegram)
|
||||
- [Pushbullet](Transports.md#transports-pushbullet)
|
||||
- [Clickatell](Transports.md#transports-clickatell)
|
||||
- [PlaySMS](Transports.md#transports-playsms)
|
||||
- [VictorOps](Transports.md#transports-victorops)
|
||||
- [Canopsis](Transports.md#transports-canopsis)
|
||||
- [osTicket](Transports.md#transports-osticket)
|
||||
- [Microsoft Teams](Transports.md#transports-msteams)
|
||||
- [Cisco Spark](Transports.md#transports-ciscospark)
|
||||
- [SMSEagle](Transports.md#transports-smseagle)
|
||||
- [Syslog](Transports.md#transports-syslog)
|
||||
- [Elasticsearch](Transports.md#transports-elasticsearch)
|
||||
- [Jira](Transports.md#transports-jira)
|
||||
|
||||
- [Entities](Entities.md)
|
||||
- [Devices](Entities.md#entity-devices)
|
||||
- [BGP Peers](Entities.md#entity-bgppeers)
|
||||
- [IPSec Tunnels](Entities.md#entity-ipsec)
|
||||
- [Memory Pools](Entities.md#entity-mempools)
|
||||
- [Ports](Entities.md#entity-ports)
|
||||
- [Processors](Entities.md#entity-processors)
|
||||
- [Storage](Entities.md#entity-storage)
|
||||
- [Sensors](Entities.md#entity-sensors)
|
||||
- [Macros](Macros.md)
|
||||
- [Device](Macros.md#macros-device)
|
||||
- [Port](Macros.md#macros-port)
|
||||
- [Time](Macros.md#macros-time)
|
||||
- [Sensors](Macros.md#macros-sensors)
|
||||
- [Misc](Macros.md#macros-misc)
|
||||
|
||||
|
||||
# <a name="about">About</a>
|
||||
|
||||
LibreNMS includes a highly customizable alerting system.
|
||||
The system requires a set of user-defined rules to evaluate the situation of each device, port, service or any other entity.
|
||||
|
||||
> You can configure all options for alerting and transports via the WebUI, config options in this document are crossed out but left for reference.
|
||||
@@ -1,101 +1,77 @@
|
||||
source: Alerting/Entities.md
|
||||
|
||||
# <a name="entities">Entities
|
||||
# Entities
|
||||
|
||||
Entities as described earlier are based on the table and column names within the database, if you are unsure of what the entity is you want then have a browse around inside MySQL using `show tables` and `desc <tablename>`.
|
||||
|
||||
## <a name="entity-devices">Devices</a>
|
||||
## Devices
|
||||
Entity | Description
|
||||
---|---
|
||||
`devices.hostname` | The device hostname
|
||||
`devices.sysName` | The device sysName
|
||||
`devices.sysDescr` | The device sysDescr
|
||||
`devices.hardware` | The device hardware
|
||||
`devices.version` | The device os version
|
||||
`devices.location` | The device location
|
||||
`devices.status` | The status of the device, 1 | up, 0 | down
|
||||
`devices.status_reason` | The reason the device was detected as down (icmp or snmp)
|
||||
`devices.ignore` | If the device is ignored this will be set to 1
|
||||
`devices.disabled` | If the device is disabled this will be set to 1
|
||||
`devices.last_polled` | The the last polled datetime (yyyy-mm-dd hh:mm:ss)
|
||||
`devices.type` | The device type such as network, server, firewall, etc.
|
||||
|
||||
__devices.hostname__ = The device hostname.
|
||||
## BGP Peers
|
||||
Entity | Description
|
||||
---|---
|
||||
`bgpPeers.astext` | This is the description of the BGP Peer
|
||||
`bgpPeers.bgpPeerIdentifier` | The IP address of the BGP Peer
|
||||
`bgpPeers.bgpPeerRemoteAs` | The AS number of the BGP Peer
|
||||
`bgpPeers.bgpPeerState` | The operational state of the BGP session
|
||||
`bgpPeers.bgpPeerAdminStatus` | The administrative state of the BGP session
|
||||
`bgpPeers.bgpLocalAddr` | The local address of the BGP session.
|
||||
|
||||
__devices.sysName__ = The device sysName.
|
||||
## IPSec Tunnels
|
||||
Entity | Description
|
||||
---|---
|
||||
`ipsec_tunnels.peer_addr` | The remote VPN peer address
|
||||
`ipsec_tunnels.local_addr` | The local VPN address
|
||||
`ipsec_tunnels.tunnel_status` | The VPN tunnels operational status.
|
||||
|
||||
__devices.sysDescr__ = The device sysDescr.
|
||||
## Memory pools
|
||||
Entity | Description
|
||||
---|---
|
||||
`mempools.mempool_type` | The memory pool type such as hrstorage, cmp and cemp
|
||||
`mempools.mempool_descr` | The description of the pool such as Physical memory, Virtual memory and System memory
|
||||
`mempools.mempool_perc` | The used percentage of the memory pool.
|
||||
|
||||
__devices.hardware__ = The device hardware.
|
||||
## Ports
|
||||
Entity | Description
|
||||
---|---
|
||||
`ports.ifDescr` | The interface description
|
||||
`ports.ifName` | The interface name
|
||||
`ports.ifSpeed` | The port speed in bps
|
||||
`ports.ifHighSpeed` | The port speed in mbps
|
||||
`ports.ifOperStatus` | The operational status of the port (up or down)
|
||||
`ports.ifAdminStatus` | The administrative status of the port (up or down)
|
||||
`ports.ifDuplex` | Duplex setting of the port
|
||||
`ports.ifMtu` | The MTU setting of the port.
|
||||
|
||||
__devices.version__ = The device os version.
|
||||
## Processors
|
||||
Entity | Description
|
||||
---|---
|
||||
`processors.processor_usage` | The usage of the processor as a percentage
|
||||
`processors.processor_descr` | The description of the processor.
|
||||
|
||||
__devices.location__ = The device location.
|
||||
## Storage
|
||||
Entity | Description
|
||||
---|---
|
||||
`storage.storage_descr` | The description of the storage
|
||||
`storage.storage_perc` | The usage of the storage as a percentage.
|
||||
|
||||
__devices.status__ = The status of the device, 1 = up, 0 = down.
|
||||
|
||||
__devices.status_reason__ = The reason the device was detected as down (icmp or snmp).
|
||||
|
||||
__devices.ignore__ = If the device is ignored this will be set to 1.
|
||||
|
||||
__devices.disabled__ = If the device is disabled this will be set to 1.
|
||||
|
||||
__devices.last_polled__ = The the last polled datetime (yyyy-mm-dd hh:mm:ss).
|
||||
|
||||
__devices.type__ = The device type such as network, server, firewall, etc.
|
||||
|
||||
## <a name="entity-bgppeers">BGP Peers</a>
|
||||
|
||||
__bgpPeers.astext__ = This is the description of the BGP Peer.
|
||||
|
||||
__bgpPeers.bgpPeerIdentifier__ = The IP address of the BGP Peer.
|
||||
|
||||
__bgpPeers.bgpPeerRemoteAs__ = The AS number of the BGP Peer.
|
||||
|
||||
__bgpPeers.bgpPeerState__ = The operational state of the BGP session.
|
||||
|
||||
__bgpPeers.bgpPeerAdminStatus__ = The administrative state of the BGP session.
|
||||
|
||||
__bgpPeers.bgpLocalAddr__ = The local address of the BGP session.
|
||||
|
||||
## <a name="entity-ipsec">IPSec Tunnels</a>
|
||||
|
||||
__ipsec_tunnels.peer_addr__ = The remote VPN peer address.
|
||||
|
||||
__ipsec_tunnels.local_addr__ = The local VPN address.
|
||||
|
||||
__ipsec_tunnels.tunnel_status__ = The VPN tunnels operational status.
|
||||
|
||||
## <a name="entity-mempools">Memory pools</a>
|
||||
|
||||
__mempools.mempool_type__ = The memory pool type such as hrstorage, cmp and cemp.
|
||||
|
||||
__mempools.mempool_descr__ = The description of the pool such as Physical memory, Virtual memory and System memory.
|
||||
|
||||
__mempools.mempool_perc__ = The used percentage of the memory pool.
|
||||
|
||||
## <a name="entity-ports">Ports</a>
|
||||
|
||||
__ports.ifDescr__ = The interface description.
|
||||
|
||||
__ports.ifName__ = The interface name.
|
||||
|
||||
__ports.ifSpeed__ = The port speed in bps.
|
||||
|
||||
__ports.ifHighSpeed__ = The port speed in mbps.
|
||||
|
||||
__ports.ifOperStatus__ = The operational status of the port (up or down).
|
||||
|
||||
__ports.ifAdminStatus__ = The administrative status of the port (up or down).
|
||||
|
||||
__ports.ifDuplex__ = Duplex setting of the port.
|
||||
|
||||
__ports.ifMtu__ = The MTU setting of the port.
|
||||
|
||||
## <a name="entity-processors">Processors</a>
|
||||
|
||||
__processors.processor_usage__ = The usage of the processor as a percentage.
|
||||
|
||||
__processors.processor_descr__ = The description of the processor.
|
||||
|
||||
## <a name="entity-storage">Storage</a>
|
||||
|
||||
__storage.storage_descr__ = The description of the storage.
|
||||
|
||||
__storage.storage_perc__ = The usage of the storage as a percentage.
|
||||
|
||||
## <a name="entity-sensors">Health / Sensors</a>
|
||||
|
||||
__sensors.sensor_desc__ = The sensors description.
|
||||
|
||||
__sensors.sensor_current__ = The current sensors value.
|
||||
|
||||
__sensors.sensor_prev__ = The previous sensor value.
|
||||
|
||||
__sensors.lastupdate__ = The sensors last updated datetime stamp.
|
||||
## Health / Sensors
|
||||
Entity | Description
|
||||
---|---
|
||||
`sensors.sensor_desc` | The sensors description.
|
||||
`sensors.sensor_current` | The current sensors value.
|
||||
`sensors.sensor_prev` | The previous sensor value.
|
||||
`sensors.lastupdate` | The sensors last updated datetime stamp.
|
||||
@@ -1,6 +1,6 @@
|
||||
source: Alerting/Macros.md
|
||||
|
||||
# <a name="macros">Macros</a>
|
||||
# Macros
|
||||
|
||||
Macros are shorthands to either portion of rules or pure SQL enhanced with placeholders.
|
||||
|
||||
@@ -25,7 +25,7 @@ Example
|
||||
((%ports.ifInOctets_rate*8) / %ports.ifSpeed)*100
|
||||
```
|
||||
|
||||
## <a name="macros-device">Device</a> (Boolean)
|
||||
## Device (Boolean)
|
||||
|
||||
Entity: `%macros.device`
|
||||
|
||||
@@ -33,7 +33,7 @@ Description: Only select devices that aren't deleted, ignored or disabled.
|
||||
|
||||
Source: `(%devices.disabled = "0" && %devices.ignore = "0")`
|
||||
|
||||
### <a name="macros-device-up">Device is up</a> (Boolean)
|
||||
### Device is up (Boolean)
|
||||
|
||||
Entity: `%macros.device_up`
|
||||
|
||||
@@ -43,7 +43,7 @@ Implies: %macros.device
|
||||
|
||||
Source: `(%devices.status = "1" && %macros.device)`
|
||||
|
||||
### <a name="macros-device-down">Device is down</a> (Boolean)
|
||||
### Device is down (Boolean)
|
||||
|
||||
Entity: `%macros.device_down`
|
||||
|
||||
@@ -53,7 +53,7 @@ Implies: %macros.device
|
||||
|
||||
Source: `(%devices.status = "0" && %macros.device)`
|
||||
|
||||
## <a name="macros-port">Port</a> (Boolean)
|
||||
## Port (Boolean)
|
||||
|
||||
Entity: `%macros.port`
|
||||
|
||||
@@ -61,7 +61,7 @@ Description: Only select ports that aren't deleted, ignored or disabled.
|
||||
|
||||
Source: `(%ports.deleted = "0" && %ports.ignore = "0" && %ports.disabled = "0")`
|
||||
|
||||
### <a name="macros-port-up">Port is up</a> (Boolean)
|
||||
### Port is up (Boolean)
|
||||
|
||||
Entity: `%macros.port_up`
|
||||
|
||||
@@ -71,7 +71,7 @@ Implies: %macros.port
|
||||
|
||||
Source: `(%ports.ifOperStatus = "up" && %ports.ifAdminStatus = "up" && %macros.port)`
|
||||
|
||||
### <a name="macros-port-down">Port is down</a> (Boolean)
|
||||
### Port is down (Boolean)
|
||||
|
||||
Entity: `%macros.port_down`
|
||||
|
||||
@@ -81,7 +81,7 @@ Implies: %macros.port
|
||||
|
||||
Source: `(%ports.ifOperStatus = "down" && %ports.ifAdminStatus != "down" && %macros.port)`
|
||||
|
||||
### <a name="macros-port-usage-perc">Port-Usage in Percent</a> (Decimal)
|
||||
### Port-Usage in Percent (Decimal)
|
||||
|
||||
Entity: `%macros.port_usage_perc`
|
||||
|
||||
@@ -89,9 +89,9 @@ Description: Return port-usage in percent.
|
||||
|
||||
Source: `((%ports.ifInOctets_rate*8) / %ports.ifSpeed)*100`
|
||||
|
||||
## <a name="macros-time">Time</a>
|
||||
## Time
|
||||
|
||||
### <a name="macros-time-now">Now</a> (Datetime)
|
||||
### Now (Datetime)
|
||||
|
||||
Entity: `%macros.now`
|
||||
|
||||
@@ -99,7 +99,7 @@ Description: Alias of MySQL's NOW()
|
||||
|
||||
Source: `NOW()`
|
||||
|
||||
### <a name="macros-time-past-Nm">Past N Minutes</a> (Datetime)
|
||||
### Past N Minutes (Datetime)
|
||||
|
||||
Entity: `%macros.past_$m`
|
||||
|
||||
@@ -111,7 +111,7 @@ Resolution: 5,10,15,30,60
|
||||
|
||||
Source: `DATE_SUB(NOW(),INTERVAL $ MINUTE)`
|
||||
|
||||
## <a name="macros-sensors">Sensors</a> (Boolean)
|
||||
## Sensors (Boolean)
|
||||
|
||||
Entity: `%macros.sensor`
|
||||
|
||||
@@ -125,7 +125,7 @@ Description: Only selects sensors that have a port linked to them, the port is u
|
||||
|
||||
Source: `(%sensors.entity_link_type = 'port' && %sensors.entity_link_index = %ports.ifIndex && %macros.port_up && %macros.device_up))`
|
||||
|
||||
## <a name="macros-misc">Misc</a> (Boolean)
|
||||
## Misc (Boolean)
|
||||
|
||||
### Packet Loss
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
source: Alerting/Rules.md
|
||||
|
||||
# <a name="rules">Rules</a>
|
||||
# Rules
|
||||
|
||||
Rules are defined using a logical language.
|
||||
The GUI provides a simple way of creating basic rules.
|
||||
Creating more complicated rules which may include maths calculations and MySQL queries can be
|
||||
done using [macros](Macros.md)
|
||||
|
||||
## <a name="rules-syntax">Syntax</a>
|
||||
## Syntax
|
||||
|
||||
Rules must consist of at least 3 elements: An __Entity__, a __Condition__ and a __Value__.
|
||||
Rules can contain braces and __Glues__.
|
||||
@@ -32,7 +32,7 @@ __Note__: The difference between `Equals` and `Like` (and its negation) is that
|
||||
|
||||
Arithmetics are allowed as well.
|
||||
|
||||
# <a name="extra">Options</a>
|
||||
# Options
|
||||
|
||||
Here are some of the other options available when adding an alerting rule:
|
||||
|
||||
@@ -44,7 +44,7 @@ Here are some of the other options available when adding an alerting rule:
|
||||
- Mute alerts: Disable sending alerts for this rule.
|
||||
- Invert match: Invert the matching rule (ie. alert on items that _don't_ match the rule).
|
||||
|
||||
## <a name="rules-examples">Examples</a>
|
||||
## Examples
|
||||
|
||||
Alert when:
|
||||
|
||||
@@ -59,7 +59,7 @@ Alert when:
|
||||
- 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="rules-procedure">Procedure</a>
|
||||
## Procedure
|
||||
You can associate a rule to a procedure by giving the URL of the procedure when creating the rule. Only links like "http://" are supported, otherwise an error will be returned. Once configured, procedure can be opened from the Alert widget through the "Open" button, which can be shown/hidden from the widget configuration box.
|
||||
|
||||
## Testing alerts
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
source: Alerting/Templates.md
|
||||
|
||||
# <a name="templates">Templates</a>
|
||||
# Templates
|
||||
|
||||
Templates can be assigned to a single or a group of rules and can contain any kind of text. There is also a default template which is used for any rule that isn't associated with a template. This template can be found under `Alert Templates` page and can be edited. It also has an option revert it back to its default content.
|
||||
|
||||
The template-parser understands `if` and `foreach` controls and replaces certain placeholders with information gathered about the alert.
|
||||
|
||||
## <a name="templates-syntax">Syntax</a>
|
||||
## Syntax
|
||||
|
||||
Controls:
|
||||
|
||||
@@ -58,7 +58,7 @@ Limit: %value.sensor_limit_low / %value.sensor_limit
|
||||
|
||||
The Default Template is a 'one-size-fit-all'. We highly recommend defining your own templates for your rules to include more specific information.
|
||||
|
||||
## <a name="templates-testing">Testing</a>
|
||||
## Testing
|
||||
|
||||
It's possible to test your new template before assigning it to a rule. To do so you can run `./scripts/test-template.php`. The script will provide the help
|
||||
info when ran without any parameters.
|
||||
@@ -70,7 +70,7 @@ As an example, if you wanted to test template ID 10 against localhost running ru
|
||||
If the rule is currently alerting for localhost then you will get the full template as expected to see on email, if it's not then you will just see the
|
||||
template without any fault information.
|
||||
|
||||
## <a name="templates-examples">Examples</a>
|
||||
## Examples
|
||||
|
||||
Default Template:
|
||||
```text
|
||||
@@ -95,7 +95,7 @@ Conditional formatting example, will display a link to the host in email or just
|
||||
|
||||
Note the use of double-quotes. Single quotes (`'`) in templates will be escaped (replaced with `\'`) in the output and should therefore be avoided.
|
||||
|
||||
## <a name="templates-included">Included</a>
|
||||
## Included
|
||||
|
||||
We include a few templates for you to use, these are specific to the type of alert rules you are creating. For example if you create a rule that would alert on BGP sessions then you can
|
||||
assign the BGP template to this rule to provide more information.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
source: Alerting/Transports.md
|
||||
|
||||
# <a name="transports">Transports</a>
|
||||
# Transports
|
||||
|
||||
Transports are located within `includes/alerts/transports.*.php` and defined as well as configured via ~~`$config['alert']['transports']['Example'] = 'Some Options'`~~.
|
||||
|
||||
@@ -24,7 +24,7 @@ $config['alert']['globals'] = true; //Include Global-Read into alert-contacts
|
||||
$config['alert']['admins'] = true; //Include Administrators into alert-contacts
|
||||
```
|
||||
|
||||
## <a name="transports-email">E-Mail</a>
|
||||
## E-Mail
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
@@ -34,15 +34,13 @@ set the devices sysContact, override the sysContact or have your users emails se
|
||||
`email@domain.com, alerting@domain.com`
|
||||
|
||||
E-Mail transport is enabled with adding the following to your `config.php`:
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['mail'] = true;
|
||||
```
|
||||
~~
|
||||
|
||||
The E-Mail transports uses the same email-configuration like the rest of LibreNMS.
|
||||
As a small reminder, here is it's configuration directives including defaults:
|
||||
~~
|
||||
|
||||
```php
|
||||
$config['email_backend'] = 'mail'; // Mail backend. Allowed: "mail" (PHP's built-in), "sendmail", "smtp".
|
||||
$config['email_from'] = NULL; // Mail from. Default: "ProjectName" <projectid@`hostname`>
|
||||
@@ -60,52 +58,47 @@ $config['email_smtp_password'] = NULL; // Password f
|
||||
$config['alert']['default_only'] = false; //Only issue to default_mail
|
||||
$config['alert']['default_mail'] = ''; //Default email
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-api">API</a>
|
||||
## API
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
API transports definitions are a bit more complex than the E-Mail configuration.
|
||||
The basis for configuration is ~~`$config['alert']['transports']['api'][METHOD]`~~ where `METHOD` can be `get`,`post` or `put`.
|
||||
This basis has to contain an array with URLs of each API to call.
|
||||
The URL can have the same placeholders as defined in the [Template-Syntax](#templates-syntax).
|
||||
The URL can have the same placeholders as defined in the [Template-Syntax](Templates#syntax).
|
||||
If the `METHOD` is `get`, all placeholders will be URL-Encoded.
|
||||
The API transport uses cURL to call the APIs, therefore you might need to install `php5-curl` or similar in order to make it work.
|
||||
__Note__: it is highly recommended to define own [Templates](#templates) when you want to use the API transport. The default template might exceed URL-length for GET requests and therefore cause all sorts of errors.
|
||||
__Note__: it is highly recommended to define own [Templates](Templates) when you want to use the API transport. The default template might exceed URL-length for GET requests and therefore cause all sorts of errors.
|
||||
|
||||
Example:
|
||||
~~
|
||||
|
||||
```php
|
||||
$config['alert']['transports']['api']['get'][] = "https://api.thirdparti.es/issue?apikey=abcdefg&subject=%title";
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-nagios">Nagios Compatible</a>
|
||||
## Nagios Compatible
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
The nagios transport will feed a FIFO at the defined location with the same format that nagios would.
|
||||
This allows you to use other Alerting-Systems to work with LibreNMS, for example [Flapjack](http://flapjack.io).
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['nagios'] = "/path/to/my.fifo"; //Flapjack expects it to be at '/var/cache/nagios3/event_stream.fifo'
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-irc">IRC</a>
|
||||
## IRC
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
The IRC transports only works together with the LibreNMS IRC-Bot.
|
||||
Configuration of the LibreNMS IRC-Bot is described [here](https://github.com/librenms/librenms/blob/master/doc/Extensions/IRC-Bot.md).
|
||||
~~
|
||||
|
||||
```php
|
||||
$config['alert']['transports']['irc'] = true;
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-slack">Slack</a>
|
||||
## Slack
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
@@ -113,16 +106,13 @@ $config['alert']['transports']['irc'] = true;
|
||||
|
||||
The Slack transport will POST the alert message to your Slack Incoming WebHook using the [attachments](https://api.slack.com/docs/message-attachments) option, you are able to specify multiple webhooks along with the relevant options to go with it. Simple html tags are stripped from the message. All options are optional, the only required value is for url, without this then no call to Slack will be made. Below is an example of how to send alerts to two channels with different customised options:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['slack'][] = array('url' => "https://hooks.slack.com/services/A12B34CDE/F56GH78JK/L901LmNopqrSTUVw2w3XYZAB4C", 'channel' => '#Alerting');
|
||||
|
||||
$config['alert']['transports']['slack'][] = array('url' => "https://hooks.slack.com/services/A12B34CDE/F56GH78JK/L901LmNopqrSTUVw2w3XYZAB4C", 'channel' => '@john', 'username' => 'LibreNMS', 'icon_emoji' => ':ghost:');
|
||||
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-slack">Rocket.chat</a>
|
||||
## Rocket.chat
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -132,10 +122,9 @@ The Rocket.chat transport will POST the alert message to your Rocket.chat Incomi
|
||||
$config['alert']['transports']['rocket'][] = array('url' => "https://rocket.url/api/v1/chat.postMessage", 'channel' => '#Alerting');
|
||||
|
||||
$config['alert']['transports']['rocket'][] = array('url' => "https://rocket.url/api/v1/chat.postMessage", 'channel' => '@john', 'username' => 'LibreNMS', 'icon_emoji' => ':ghost:');
|
||||
|
||||
```
|
||||
|
||||
## <a name="transports-hipchat">HipChat</a>
|
||||
## HipChat
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
@@ -166,7 +155,6 @@ for details on acceptable values.
|
||||
|
||||
Below are two examples of sending messages to a HipChat room.
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['hipchat'][] = array("url" => "https://api.hipchat.com/v1/rooms/message?auth_token=9109jawregoaih",
|
||||
"room_id" => "1234567",
|
||||
@@ -179,14 +167,13 @@ $config['alert']['transports']['hipchat'][] = array("url" => "https://api.hipcha
|
||||
"notify" => 1,
|
||||
"message_format" => "text");
|
||||
```
|
||||
~~
|
||||
|
||||
> Note: The default message format for HipChat messages is HTML. It is
|
||||
> recommended that you specify the `text` message format to prevent unexpected
|
||||
> results, such as HipChat attempting to interpret angled brackets (`<` and
|
||||
> `>`).
|
||||
|
||||
## <a name="transports-pagerduty">PagerDuty</a>
|
||||
## PagerDuty
|
||||
|
||||
> You can configure these options within the WebUI now, please avoid setting these options within config.php
|
||||
|
||||
@@ -198,17 +185,15 @@ All you need is to create a Service with type Generic API on your PagerDuty dash
|
||||
|
||||
Now copy your API-Key from the newly created Service and setup the transport like:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['pagerduty'] = 'MYAPIKEYGOESHERE';
|
||||
```
|
||||
~~
|
||||
|
||||
That's it!
|
||||
|
||||
__Note__: Currently ACK notifications are not transported to PagerDuty, This is going to be fixed within the next major version (version by date of writing: 2015.05)
|
||||
|
||||
## <a name="transports-pushover">Pushover</a>
|
||||
## Pushover
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -218,18 +203,15 @@ Firstly you need to create a new Application (called LibreNMS, for example) in y
|
||||
|
||||
Now copy your API Token/Key from the newly created Application and setup the transport in your config.php like:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['pushover'][] = array(
|
||||
"appkey" => 'APPLICATIONAPIKEYGOESHERE',
|
||||
"userkey" => 'USERKEYGOESHERE',
|
||||
);
|
||||
```
|
||||
~~
|
||||
|
||||
To modify the Critical alert sound, add the 'sound_critical' parameter, example:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['pushover'][] = array(
|
||||
"appkey" => 'APPLICATIONAPIKEYGOESHERE',
|
||||
@@ -237,35 +219,30 @@ $config['alert']['transports']['pushover'][] = array(
|
||||
"sound_critical" => 'siren',
|
||||
);
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-boxcar">Boxcar</a>
|
||||
## Boxcar
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
Enabling Boxcar support is super easy.
|
||||
Copy your access token from the Boxcar app or from the Boxcar.io website and setup the transport in your config.php like:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['boxcar'][] = array(
|
||||
"access_token" => 'ACCESSTOKENGOESHERE',
|
||||
);
|
||||
```
|
||||
~~
|
||||
|
||||
To modify the Critical alert sound, add the 'sound_critical' parameter, example:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['boxcar'][] = array(
|
||||
"access_token" => 'ACCESSTOKENGOESHERE',
|
||||
"sound_critical" => 'detonator-charge',
|
||||
);
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-telegram">Telegram</a>
|
||||
## Telegram
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -285,20 +262,18 @@ $config['alert']['transports']['boxcar'][] = array(
|
||||
6. Now create a new "Telegram transport" in LibreNMS (Global Settings -> Alerting Settings -> Telegram transport).
|
||||
Click on 'Add Telegram config' and put your chat id and token into the relevant box.
|
||||
|
||||
## <a name="transports-pushbullet">Pushbullet</a>
|
||||
## Pushbullet
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
Enabling Pushbullet is a piece of cake.
|
||||
Get your Access Token from your Pushbullet's settings page and set it in your config like:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['pushbullet'] = 'MYFANCYACCESSTOKEN';
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-clickatell">Clickatell</a>
|
||||
## Clickatell
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -306,16 +281,14 @@ Clickatell provides a REST-API requiring an Authorization-Token and at least one
|
||||
Please consult Clickatell's documentation regarding number formatting.
|
||||
Here an example using 3 numbers, any amount of numbers is supported:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['clickatell']['token'] = 'MYFANCYACCESSTOKEN';
|
||||
$config['alert']['transports']['clickatell']['to'][] = '+1234567890';
|
||||
$config['alert']['transports']['clickatell']['to'][] = '+1234567891';
|
||||
$config['alert']['transports']['clickatell']['to'][] = '+1234567892';
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-playsms">PlaySMS</a>
|
||||
## PlaySMS
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -323,7 +296,6 @@ PlaySMS is an open source SMS-Gateway that can be used via their HTTP-API using
|
||||
Please consult PlaySMS's documentation regarding number formatting.
|
||||
Here an example using 3 numbers, any amount of numbers is supported:
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['playsms']['url'] = 'https://localhost/index.php?app=ws';
|
||||
$config['alert']['transports']['playsms']['user'] = 'user1';
|
||||
@@ -332,9 +304,8 @@ $config['alert']['transports']['playsms']['from'] = '+1234567892'; //Optional
|
||||
$config['alert']['transports']['playsms']['to'][] = '+1234567890';
|
||||
$config['alert']['transports']['playsms']['to'][] = '+1234567891';
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-victorops">VictorOps</a>
|
||||
## VictorOps
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -346,13 +317,11 @@ The URL provided will have $routing_key at the end, you need to change this to s
|
||||
|
||||
`https://alert.victorops.com/integrations/generic/20132414/alert/2f974ce1-08fc-4dg8-a4f4-9aee6cf35c98/librenms`
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['victorops']['url'] = 'https://alert.victorops.com/integrations/generic/20132414/alert/2f974ce1-08fc-4dg8-a4f4-9aee6cf35c98/librenms';
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-canopsis">Canopsis</a>
|
||||
## Canopsis
|
||||
|
||||
Canopsis is a hypervision tool. LibreNMS can send alerts to Canopsis which are then converted to canopsis events. To configure the transport, go to:
|
||||
|
||||
@@ -360,7 +329,6 @@ Global Settings -> Alerting Settings -> Canopsis Transport.
|
||||
|
||||
You will need to fill this paramaters :
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['canopsis']['host'] = 'www.xxx.yyy.zzz';
|
||||
$config['alert']['transports']['canopsis']['port'] = '5672';
|
||||
@@ -368,13 +336,12 @@ $config['alert']['transports']['canopsis']['user'] = 'admin';
|
||||
$config['alert']['transports']['canopsis']['passwd'] = 'my_password';
|
||||
$config['alert']['transports']['canopsis']['vhost'] = 'canopsis';
|
||||
```
|
||||
~~
|
||||
|
||||
For more information about canopsis and its events, take a look here :
|
||||
http://www.canopsis.org/
|
||||
http://www.canopsis.org/wp-content/themes/canopsis/doc/sakura/user-guide/event-spec.html
|
||||
|
||||
## <a name="transports-osticket">osTicket</a>
|
||||
## osTicket
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -384,14 +351,12 @@ Global Settings -> Alerting Settings -> osTicket Transport.
|
||||
|
||||
This can also be done manually in config.php :
|
||||
|
||||
~~
|
||||
```php
|
||||
$config['alert']['transports']['osticket']['url'] = 'http://osticket.example.com/api/http.php/tickets.json';
|
||||
$config['alert']['transports']['osticket']['token'] = '123456789';
|
||||
```
|
||||
~~
|
||||
|
||||
## <a name="transports-msteams">Microsoft Teams</a>
|
||||
## Microsoft Teams
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -401,13 +366,11 @@ Global Settings -> Alerting Settings -> Microsoft Teams Transport.
|
||||
|
||||
This can also be done manually in config.php :
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['msteams']['url'] = 'https://outlook.office365.com/webhook/123456789';
|
||||
```
|
||||
~
|
||||
|
||||
## <a name="transports-ciscospark">Cisco Spark</a>
|
||||
## Cisco Spark
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -424,14 +387,12 @@ Global Settings -> Alerting Settings -> Cisco Spark transport.
|
||||
|
||||
This can also be done manually in config.php :
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['ciscospark']['token'] = '1234567890QWERTYUIOP';
|
||||
$config['alert']['transports']['ciscospark']['roomid'] = '1234567890QWERTYUIOP';
|
||||
```
|
||||
~
|
||||
|
||||
## <a name="transports-smseagle">SMSEagle</a>
|
||||
## SMSEagle
|
||||
|
||||
[Using a proxy?](../Support/Configuration.md#proxy-support)
|
||||
|
||||
@@ -439,7 +400,6 @@ SMSEagle is a hardware SMS Gateway that can be used via their HTTP-API using a U
|
||||
Please consult their documentation at [www.smseagle.eu](http://www.smseagle.eu)
|
||||
Destination numbers are one per line, with no spaces. They can be in either local or international dialling format.
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['smseagle']['url'] = 'ip.add.re.ss';
|
||||
$config['alert']['transports']['smseagle']['user'] = 'smseagle_user';
|
||||
@@ -447,44 +407,38 @@ $config['alert']['transports']['smseagle']['token'] = 'smseagle_user_password';
|
||||
$config['alert']['transports']['smseagle']['to'][] = '+3534567890';
|
||||
$config['alert']['transports']['smseagle']['to'][] = '0834567891';
|
||||
```
|
||||
~
|
||||
|
||||
## <a name="transports-syslog">Syslog</a>
|
||||
## Syslog
|
||||
|
||||
You can have LibreNMS emit alerts as syslogs complying with RFC 3164.
|
||||
More information on RFC 3164 can be found here: https://tools.ietf.org/html/rfc3164
|
||||
Example output: `<26> Mar 22 00:59:03 librenms.host.net librenms[233]: [Critical] network.device.net: Port Down - port_id => 98939; ifDescr => xe-1/1/0;`
|
||||
Each fault will be sent as a separate syslog.
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['syslog']['syslog_host'] = '127.0.0.1';
|
||||
$config['alert']['transports']['syslog']['syslog_port'] = 514;
|
||||
$config['alert']['transports']['syslog']['syslog_facility'] = 3;
|
||||
```
|
||||
~
|
||||
|
||||
## <a name="transports-elasticsearch">Elasticsearch</a>
|
||||
## Elasticsearch
|
||||
|
||||
You can have LibreNMS emit alerts to an elasticsearch database. Each fault will be sent as a separate document.
|
||||
The index pattern uses strftime() formatting.
|
||||
The proxy setting uses the proxy set in config.php if true and does not if false; this allows you to use local servers.
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['elasticsearch']['es_host'] = '127.0.0.1';
|
||||
$config['alert']['transports']['elasticsearch']['es_port'] = 9200;
|
||||
$config['alert']['transports']['elasticsearch']['es_index'] = 'librenms-%Y.%m.%d';
|
||||
$config['alert']['transports']['elasticsearch']['es_proxy'] = false;
|
||||
```
|
||||
~
|
||||
|
||||
## <a name="transports-jira">JIRA</a>
|
||||
## JIRA
|
||||
|
||||
You can have LibreNMS create issues on a Jira instance for critical and warning alerts. The Jira transport only sets summary and description fiels. Therefore your Jira project must not have any other mandatory field for the provided issuetype. The config fields that need to set are Jira URL, Jira username, Jira password, Project key, and issue type.
|
||||
Currently http authentication is used to access Jira and Jira username and password will be stored as cleartext in the LibreNMS database.
|
||||
|
||||
~
|
||||
```php
|
||||
$config['alert']['transports']['jira']['url'] = 'https://myjira.mysite.com';
|
||||
$config['alert']['transports']['jira']['username'] = 'myjirauser';
|
||||
@@ -492,5 +446,3 @@ $config['alert']['transports']['jira']['password'] = 'myjirapass';
|
||||
$config['alert']['transports']['jira']['prjkey'][] = 'JIRAPROJECTKEY';
|
||||
$config['alert']['transports']['jira']['issuetype'][] = 'Myissuetype';
|
||||
```
|
||||
~
|
||||
|
||||
|
||||
62
doc/Alerting/index.md
Normal file
62
doc/Alerting/index.md
Normal file
@@ -0,0 +1,62 @@
|
||||
source: Alerting/index.md
|
||||
Table of Content:
|
||||
|
||||
- [About](#about)
|
||||
- [Rules](Rules.md)
|
||||
- [Syntax](Rules.md#syntax)
|
||||
- [Options](Rules.md#options)
|
||||
- [Examples](Rules.md#examples)
|
||||
- [Procedure](Rules.md#procedure)
|
||||
- [Templates](Templates.md)
|
||||
- [Syntax](Templates.md#syntax)
|
||||
- [Testing](Templates.md#testing)
|
||||
- [Examples](Templates.md#examples)
|
||||
- [Included](Templates.md#included)
|
||||
- [Transports](Transports.md)
|
||||
- [E-Mail](Transports.md#e-mail)
|
||||
- [API](Transports.md#api)
|
||||
- [Nagios-Compatible](Transports.md#nagios-compatible)
|
||||
- [IRC](Transports.md#irc)
|
||||
- [Slack](Transports.md#slack)
|
||||
- [Rocket.chat](Transports.md#rocketchat)
|
||||
- [HipChat](Transports.md#hipchat)
|
||||
- [PagerDuty](Transports.md#pagerduty)
|
||||
- [Pushover](Transports.md#pushover)
|
||||
- [Boxcar](Transports.md#boxcar)
|
||||
- [Telegram](Transports.md#telegram)
|
||||
- [Pushbullet](Transports.md#pushbullet)
|
||||
- [Clickatell](Transports.md#clickatell)
|
||||
- [PlaySMS](Transports.md#playsms)
|
||||
- [VictorOps](Transports.md#victorops)
|
||||
- [Canopsis](Transports.md#canopsis)
|
||||
- [osTicket](Transports.md#osticket)
|
||||
- [Microsoft Teams](Transports.md#microsoftteams)
|
||||
- [Cisco Spark](Transports.md#ciscospark)
|
||||
- [SMSEagle](Transports.md#smseagle)
|
||||
- [Syslog](Transports.md#syslog)
|
||||
- [Elasticsearch](Transports.md#elasticsearch)
|
||||
- [Jira](Transports.md#jira)
|
||||
|
||||
- [Entities](Entities.md)
|
||||
- [Devices](Entities.md#devices)
|
||||
- [BGP Peers](Entities.md#bgppeers)
|
||||
- [IPSec Tunnels](Entities.md#ipsec)
|
||||
- [Memory Pools](Entities.md#entity-mempools)
|
||||
- [Ports](Entities.md#entity-ports)
|
||||
- [Processors](Entities.md#entity-processors)
|
||||
- [Storage](Entities.md#entity-storage)
|
||||
- [Sensors](Entities.md#entity-sensors)
|
||||
- [Macros](Macros.md)
|
||||
- [Device](Macros.md#macros-device)
|
||||
- [Port](Macros.md#macros-port)
|
||||
- [Time](Macros.md#macros-time)
|
||||
- [Sensors](Macros.md#macros-sensors)
|
||||
- [Misc](Macros.md#macros-misc)
|
||||
|
||||
|
||||
# About
|
||||
|
||||
LibreNMS includes a highly customizable alerting system.
|
||||
The system requires a set of user-defined rules to evaluate the situation of each device, port, service or any other entity.
|
||||
|
||||
> You can configure all options for alerting and transports via the WebUI, config options in this document are crossed out but left for reference.
|
||||
@@ -321,7 +321,7 @@ The varying options after that are to support the different transports.
|
||||
|
||||
### Alerting
|
||||
|
||||
[Alerting](../Alerting/Alerting.md)
|
||||
[Alerting](../Alerting/index.md)
|
||||
|
||||
### Billing
|
||||
|
||||
|
||||
224
mkdocs.yml
224
mkdocs.yml
@@ -16,115 +16,115 @@ repo_url: https://github.com/librenms/librenms
|
||||
repo_name: GitHub
|
||||
google_analytics: ['UA-79149977-2', 'docs.librenms.org']
|
||||
pages:
|
||||
- Home: index.md
|
||||
- General:
|
||||
- General/Acknowledgement.md
|
||||
- General/Callback-Stats-and-Privacy.md
|
||||
- General/Changelog.md
|
||||
- Code of Conduct: General/CODE_OF_CONDUCT.md
|
||||
- General/Contributing.md
|
||||
- General/Credits.md
|
||||
- General/Updating.md
|
||||
- General/Releases.md
|
||||
- General/Security.md
|
||||
- General/Welcome-to-Observium-users.md
|
||||
- Installation:
|
||||
- Installing LibreNMS: Installation/Installing-LibreNMS.md
|
||||
- Ubuntu VM Image: Installation/Ubuntu-image.md
|
||||
- CentOS VM Image: Installation/CentOS-image.md
|
||||
- Ubuntu 16.04 (Nginx): Installation/Installation-Ubuntu-1604-Nginx.md
|
||||
- Ubuntu 16.04 (Apache): Installation/Installation-Ubuntu-1604-Apache.md
|
||||
- CentOS 7 (Nginx): Installation/Installation-CentOS-7-Nginx.md
|
||||
- CentOS 7 (Apache): Installation/Installation-CentOS-7-Apache.md
|
||||
- Older Docs: Installation/Installing-LibreNMS.md
|
||||
- Migrating from Observium: Installation/Migrating-from-Observium.md
|
||||
- Extensions:
|
||||
- Extensions/Applications.md
|
||||
- Extensions/Authentication.md
|
||||
- Extensions/Auto-Discovery.md
|
||||
- Extensions/Agent-Setup.md
|
||||
- Extensions/Billing-Module.md
|
||||
- Extensions/Component.md
|
||||
- Extensions/Dell-OpenManage.md
|
||||
- Extensions/Device-Groups.md
|
||||
- Extensions/Distributed-Poller.md
|
||||
- Extensions/Email-Alerting.md
|
||||
- Extensions/Globe-Frontpage.md
|
||||
- Extensions/Graylog.md
|
||||
- Extensions/IRC-Bot.md
|
||||
- Extensions/IRC-Bot-Extensions.md
|
||||
- Extensions/Interface-Description-Parsing.md
|
||||
- Extensions/MIB-based-polling.md
|
||||
- Extensions/Memcached.md
|
||||
- Extensions/Metric-Storage.md
|
||||
- Extensions/Network-Map.md
|
||||
- Extensions/NFSen.md
|
||||
- Extensions/Oxidized.md
|
||||
- Extensions/PeeringDB.md
|
||||
- Extensions/Plugin-System.md
|
||||
- Extensions/Poller-Service.md
|
||||
- Extensions/Port-Description-Parser.md
|
||||
- Extensions/Proxmox.md
|
||||
- Extensions/RRDCached.md
|
||||
- Extensions/RRDTune.md
|
||||
- Extensions/SNMP-Proxy.md
|
||||
- Extensions/SNMP-Trap-Handler.md
|
||||
- Extensions/Services.md
|
||||
- Extensions/Smokeping.md
|
||||
- Extensions/Sub-Directory.md
|
||||
- Extensions/Syslog.md
|
||||
- Extensions/Two-Factor-Auth.md
|
||||
- Extensions/Varnish.md
|
||||
- API: API/API-Docs.md
|
||||
- Alerting: Alerting/Alerting.md
|
||||
- Support:
|
||||
- Support/1-Minute-Polling.md
|
||||
- Support/Configuration.md
|
||||
- Support/Discovery Support.md
|
||||
- Support/Example-Hardware-Setup.md
|
||||
- Support/FAQ.md
|
||||
- Support/Features.md
|
||||
- Support/Install Validation.md
|
||||
- Support/Performance.md
|
||||
- Support/Poller Support.md
|
||||
- Support/Remote-Monitoring-VPN.md
|
||||
- Support/SNMP-Configuration-Examples.md
|
||||
- Support/SSL-Configuration.md
|
||||
- Developing:
|
||||
- Developing/Using-Git.md
|
||||
- Developing/Code-Guidelines.md
|
||||
- Developing/Style-Guidelines.md
|
||||
- Developing/Validating-Code.md
|
||||
- Developing/Code-Structure.md
|
||||
- Developing/Creating-Documentation.md
|
||||
- Adding support for a new OS: Developing/Support-New-OS.md
|
||||
- Developing/Dynamic-Config.md
|
||||
- Developing/Sensor-State-Support.md
|
||||
- Developing/Merging-Pull-Requests.md
|
||||
- Developing/Creating-Release.md
|
||||
- hidden:
|
||||
- Alerting/Rules.md
|
||||
- Alerting/Templates.md
|
||||
- Alerting/Transports.md
|
||||
- Alerting/Entities.md
|
||||
- Alerting/Macros.md
|
||||
- Alerting/Rules.md
|
||||
- Developing/os/Initial-Detection.md
|
||||
- Developing/os/Mem-CPU-Information.md
|
||||
- Developing/os/Test-Units.md
|
||||
- Developing/os/Health-Information.md
|
||||
- Developing/os/Wireless-Sensors.md
|
||||
- Developing/os/Custom-Graphs.md
|
||||
- Extensions/Agent-Setup.md
|
||||
- Extensions/Alerting.md
|
||||
- Extensions/metrics/InfluxDB.md
|
||||
- Extensions/metrics/Graphite.md
|
||||
- Extensions/metrics/OpenTSDB.md
|
||||
- Extensions/RRDCached-Security.md
|
||||
- Installation/Installation-Ubuntu-1404-Nginx.md
|
||||
- Installation/Installation-Ubuntu-1404-Apache.md
|
||||
- Installation/Installation-Ubuntu-1404-Lighttpd.md
|
||||
- Installation/Installation-CentOS-6-Apache-Nginx.md
|
||||
- Installation/Installation-(Debian-Ubuntu).md
|
||||
- Installation/Installation-(RHEL-CentOS).md
|
||||
- Support/Support-New-OS.md
|
||||
- Home: index.md
|
||||
- General:
|
||||
- General/Acknowledgement.md
|
||||
- General/Callback-Stats-and-Privacy.md
|
||||
- General/Changelog.md
|
||||
- Code of Conduct: General/CODE_OF_CONDUCT.md
|
||||
- General/Contributing.md
|
||||
- General/Credits.md
|
||||
- General/Updating.md
|
||||
- General/Releases.md
|
||||
- General/Security.md
|
||||
- General/Welcome-to-Observium-users.md
|
||||
- Installation:
|
||||
- Installing LibreNMS: Installation/Installing-LibreNMS.md
|
||||
- Ubuntu VM Image: Installation/Ubuntu-image.md
|
||||
- CentOS VM Image: Installation/CentOS-image.md
|
||||
- Ubuntu 16.04 (Nginx): Installation/Installation-Ubuntu-1604-Nginx.md
|
||||
- Ubuntu 16.04 (Apache): Installation/Installation-Ubuntu-1604-Apache.md
|
||||
- CentOS 7 (Nginx): Installation/Installation-CentOS-7-Nginx.md
|
||||
- CentOS 7 (Apache): Installation/Installation-CentOS-7-Apache.md
|
||||
- Older Docs: Installation/Installing-LibreNMS.md
|
||||
- Migrating from Observium: Installation/Migrating-from-Observium.md
|
||||
- Extensions:
|
||||
- Extensions/Applications.md
|
||||
- Extensions/Authentication.md
|
||||
- Extensions/Auto-Discovery.md
|
||||
- Extensions/Agent-Setup.md
|
||||
- Extensions/Billing-Module.md
|
||||
- Extensions/Component.md
|
||||
- Extensions/Dell-OpenManage.md
|
||||
- Extensions/Device-Groups.md
|
||||
- Extensions/Distributed-Poller.md
|
||||
- Extensions/Email-Alerting.md
|
||||
- Extensions/Globe-Frontpage.md
|
||||
- Extensions/Graylog.md
|
||||
- Extensions/IRC-Bot.md
|
||||
- Extensions/IRC-Bot-Extensions.md
|
||||
- Extensions/Interface-Description-Parsing.md
|
||||
- Extensions/MIB-based-polling.md
|
||||
- Extensions/Memcached.md
|
||||
- Extensions/Metric-Storage.md
|
||||
- Extensions/Network-Map.md
|
||||
- Extensions/NFSen.md
|
||||
- Extensions/Oxidized.md
|
||||
- Extensions/PeeringDB.md
|
||||
- Extensions/Plugin-System.md
|
||||
- Extensions/Poller-Service.md
|
||||
- Extensions/Port-Description-Parser.md
|
||||
- Extensions/Proxmox.md
|
||||
- Extensions/RRDCached.md
|
||||
- Extensions/RRDTune.md
|
||||
- Extensions/SNMP-Proxy.md
|
||||
- Extensions/SNMP-Trap-Handler.md
|
||||
- Extensions/Services.md
|
||||
- Extensions/Smokeping.md
|
||||
- Extensions/Sub-Directory.md
|
||||
- Extensions/Syslog.md
|
||||
- Extensions/Two-Factor-Auth.md
|
||||
- Extensions/Varnish.md
|
||||
- API: API/API-Docs.md
|
||||
- Alerting: Alerting/index.md
|
||||
- Support:
|
||||
- Support/1-Minute-Polling.md
|
||||
- Support/Configuration.md
|
||||
- Support/Discovery Support.md
|
||||
- Support/Example-Hardware-Setup.md
|
||||
- Support/FAQ.md
|
||||
- Support/Features.md
|
||||
- Support/Install Validation.md
|
||||
- Support/Performance.md
|
||||
- Support/Poller Support.md
|
||||
- Support/Remote-Monitoring-VPN.md
|
||||
- Support/SNMP-Configuration-Examples.md
|
||||
- Support/SSL-Configuration.md
|
||||
- Developing:
|
||||
- Developing/Using-Git.md
|
||||
- Developing/Code-Guidelines.md
|
||||
- Developing/Style-Guidelines.md
|
||||
- Developing/Validating-Code.md
|
||||
- Developing/Code-Structure.md
|
||||
- Developing/Creating-Documentation.md
|
||||
- Adding support for a new OS: Developing/Support-New-OS.md
|
||||
- Developing/Dynamic-Config.md
|
||||
- Developing/Sensor-State-Support.md
|
||||
- Developing/Merging-Pull-Requests.md
|
||||
- Developing/Creating-Release.md
|
||||
- hidden:
|
||||
- Alerting/Rules.md
|
||||
- Alerting/Templates.md
|
||||
- Alerting/Transports.md
|
||||
- Alerting/Entities.md
|
||||
- Alerting/Macros.md
|
||||
- Alerting/Rules.md
|
||||
- Developing/os/Initial-Detection.md
|
||||
- Developing/os/Mem-CPU-Information.md
|
||||
- Developing/os/Test-Units.md
|
||||
- Developing/os/Health-Information.md
|
||||
- Developing/os/Wireless-Sensors.md
|
||||
- Developing/os/Custom-Graphs.md
|
||||
- Extensions/Agent-Setup.md
|
||||
- Extensions/Alerting.md
|
||||
- Extensions/metrics/InfluxDB.md
|
||||
- Extensions/metrics/Graphite.md
|
||||
- Extensions/metrics/OpenTSDB.md
|
||||
- Extensions/RRDCached-Security.md
|
||||
- Installation/Installation-Ubuntu-1404-Nginx.md
|
||||
- Installation/Installation-Ubuntu-1404-Apache.md
|
||||
- Installation/Installation-Ubuntu-1404-Lighttpd.md
|
||||
- Installation/Installation-CentOS-6-Apache-Nginx.md
|
||||
- Installation/Installation-(Debian-Ubuntu).md
|
||||
- Installation/Installation-(RHEL-CentOS).md
|
||||
- Support/Support-New-OS.md
|
||||
|
||||
Reference in New Issue
Block a user