Skip to main content

Fluentd monitoring with Netdata

Fluentd is an open source data collector for unified logging layer.

This module will monitor one or more Fluentd servers, depending on your configuration. It gathers metrics from plugin endpoint provided by in_monitor plugin.

Requirements#

  • fluentd with enabled monitoring agent

Charts#

It produces the following charts:

  • Plugin Retry Count in count
  • Plugin Buffer Queue Length in queue length
  • Plugin Buffer Total Size in buffer

Configuration#

Edit the go.d/fluentd.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/fluentd.conf

Needs only url. Here is an example for 2 servers:

jobs:
- name: local
url: http://127.0.0.1:24220
- name: local_with_filtering
url: http://127.0.0.1:24220
permit_plugin_id: '!monitor_agent !dummy *'
- name: remote
url: http://203.0.113.10:24220

By default this module collects statistics for all plugins. Filter plugins syntax: simple patterns.

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the fluentd collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m fluentd

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community