Skip to main content

Logstash monitoring with Netdata

Logstash is an open-source data processing pipeline that allows you to collect, process, and load data into Elasticsearch.

This module will monitor one or more Logstash instances, depending on your configuration.

Metrics

All metrics have "logstash." prefix.

MetricScopeDimensionsUnits
jvm_threadsglobalthreadscount
jvm_mem_heap_usedglobalin_usepercentage
jvm_mem_heapglobalcommitted, usedKiB
jvm_mem_pools_edenglobalcommitted, usedKiB
jvm_mem_pools_survivorglobalcommitted, usedKiB
jvm_mem_pools_oldglobalcommitted, usedKiB
jvm_gc_collector_countglobaleden, oldcounts/s
jvm_gc_collector_timeglobaleden, oldms
open_file_descriptorsglobalopenfd
eventglobalin, filtered, outevents/s
event_durationglobalevent, queueseconds
uptimeglobaluptimeseconds
pipeline_eventpiepelinein, filtered, outevents/s
pipeline_eventpiepelineevent, queueseconds

Configuration

Edit the go.d/logstash.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/logstash.conf

Here is a simple example for local and remote server:

jobs:
- name: local
url: http://localhost:9600

- name: remote
url: http://203.0.113.10:9600

For all available options please see module configuration file.

Troubleshooting

To troubleshoot issues with the logstash 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.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the go.d.plugin to debug the collector:

    ./go.d.plugin -d -m logstash

Was this page helpful?

Contribute