2.0 KiB
source: Extensions/Graylog.md
Graylog integration
We have simple integration for Graylog, you will be able to view any logs from within LibreNMS that have been parsed by the syslog input from within Graylog itself. This includes logs from devices which aren't in LibreNMS still, you can also see logs for a specific device under the logs section for the device.
Currently, LibreNMS does not associate shortnames from Graylog with full FQDNS. If you have your devices in LibreNMS using full FQDNs, such as hostname.example.com, be aware that rsyslogd, by default, sends the shortname only. To fix this, add
$PreserveFQDN on
to your rsyslog config to send the full FQDN so device logs will be associated correctly in LibreNMS
Graylog itself isn't included within LibreNMS, you will need to install this separately either on the same infrastructure as LibreNMS or as a totally standalone appliance.
Config is simple, here's an example:
$config['graylog']['server'] = 'http://127.0.0.1';
$config['graylog']['port'] = 12900;
$config['graylog']['username'] = 'admin';
$config['graylog']['password'] = 'admin';
$config['graylog']['version'] = '2.1';
Since Graylog 2.1, the default API path is /api/
If you are running a version earlier than Graylog then please set $config['graylog']['version'] to the version
number of your Graylog install.
If you have altered the default uri for your Graylog setup then you can override the default of /api/ using
$config['graylog']['base_uri'] = '/somepath/';
If you choose to use another user besides the admin user, please note that currently you must give the user "admin" permissions from within Graylog, "read" permissions alone are not sufficient.
If you have enabled TLS for the Graylog API and you are using a self-signed certificate, please make sure that the certificate is trusted by your LibreNMS host, otherwise the connection will fail.
Additionally, the certificate's Common Name (CN) has to match the FQDN or IP address specified in $config['graylog']['server'].