Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update distributed poller docs intro #11721

Merged
merged 1 commit into from May 28, 2020
Merged

Update distributed poller docs intro #11721

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 18 additions & 8 deletions doc/Extensions/Distributed-Poller.md
View file
Open in desktop
Expand Up @@ -3,11 +3,17 @@ path: blob/master/doc/

# Distributed Poller

LibreNMS has the ability to distribute polling of devices to other machines.

These machines can be in a different physical location and therefore
minimize network latency for devices that are a considerable distance
away or are behind NAT firewalls.
A normal install contains all parts of LibreNMS:
* Poller/Discovery/etc workers
* RRD (Time series data store) *
* Database *
* Webserver (Web UI/API) *

\* may only be installed on one server (however, some can be clustered)

Distributed Polling allows the workers to be spread across additional
servers for horizontal scaling. Distributed polling is not intended for
remote polling.

Devices can be grouped together into a `poller_group` to pin these
devices to a single or a group of designated pollers.
Expand Down Expand Up @@ -85,9 +91,7 @@ files directly.
### Database Server

MySQL / MariaDB - At the moment these are the only database servers
that are supported, work is being done to ensure MySQL Strict mode is
also supported but this should be considered to be incomplete still
and therefor disabled.
that are supported.

The pollers, web and API layers should all be able to access the
database server directly.
Expand Down Expand Up @@ -151,6 +155,12 @@ It's not necessary to run discovery services on all pollers. In fact,
you should only run one discovery process per poller group. Designate
a single poller to run discovery (or a separate server if required).

### Configuration

Settings in config.php should be copied to all servers as they only apply locally.

One way around this is to set settings in the database via the web ui or `./lnms config:set`

### Config sample

The following config is taken from a live setup which consists of a
Expand Down