juggernaut
editjuggernaut
edit- Version: 3.0.2
- Released on: 2016-07-14
- Changelog
- Compatible: 5.1.1.1, 5.0.0, 2.4.1, 2.4.0, 2.3.4
This plugin does not ship with Logstash by default, but it is easy to install by running bin/logstash-plugin install logstash-output-juggernaut.
Push messages to the juggernaut websockets server:
Wraps Websockets and supports other methods (including xhr longpolling) This is basically, just an extension of the redis output (Juggernaut pulls messages from redis). But it pushes messages to a particular channel and formats the messages in the way juggernaut expects.
Synopsis
editThis plugin supports the following configuration options:
Required configuration options:
juggernaut {
channels => ...
}
Available configuration options:
Details
edit
channels
edit- This is a required setting.
- Value type is array
- There is no default value for this setting.
List of channels to which to publish. Dynamic names are
valid here, for example logstash-%{type}.
codec
edit- Value type is codec
-
Default value is
"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.
enable_metric
edit- Value type is boolean
-
Default value is
true
Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.
host
edit- Value type is string
-
Default value is
"127.0.0.1"
The hostname of the redis server to which juggernaut is listening.
id
edit- Value type is string
- There is no default value for this setting.
Add a unique ID to the plugin instance, this ID is used for tracking
information for a specific configuration of the plugin.
output {
stdout {
id => "ABC"
}
}
If you don’t explicitely set this variable Logstash will generate a unique name.
message_format
edit- Value type is string
- There is no default value for this setting.
How should the message be formatted before pushing to the websocket.