For other versions, see theVersioned plugin docs.
For plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-output-ganglia. See Working with plugins for more details.
For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github.For the list of Elastic supported plugins, please consult the Elastic Support Matrix.
This output allows you to pull metrics from your logs and ship them toganglia’s gmond. This is heavily based on the graphite output.
This plugin supports the following configuration options plus the Common Options described later.
| Setting | Input type | Required |
|---|---|---|
No |
||
No |
||
No |
||
No |
||
Yes |
||
string, one of |
No |
|
No |
||
string, one of |
No |
|
No |
||
Yes |
Also see Common Options for a list of options supported by alloutput plugins.
60Maximum time in seconds between gmetric calls for this metric.
The metric to use. This supports dynamic strings like %{host}
string, int8, uint8, int16, uint16, int32, uint32, float, double"uint8"The type of value for this metric.
zero, positive, negative, both, unspecified"both"Metric slope, represents metric behavior
""Gmetric units for metric, such as "kb/sec" or "ms" or whatever unitthis metric uses.
The value to use. This supports dynamic strings like %{bytes}It will be coerced to a floating point value. Values which cannot becoerced will zero (0)
The following configuration options are supported by all output plugins:
"plain"The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output without needing a separate filter in your Logstash pipeline.
trueDisable or enable metric logging for this specific plugin instance.By default we record all the metrics we can, but you can disable metrics collectionfor a specific plugin.
Add a unique ID to the plugin configuration. If no ID is specified, Logstash will generate one.It is strongly recommended to set this ID in your configuration. This is particularly usefulwhen you have two or more plugins of the same type. For example, if you have 2 ganglia outputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { ganglia { id => "my_plugin_id" }}