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-input-xmpp
. 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 input allows you to receive events over XMPP/Jabber.
This plugin can be used for accepting events from humans or applicationsXMPP, or you can use it for PubSub or general message passing for logstash tologstash.
This plugin supports the following configuration options plus the Common Options described later.
Also see Common Options for a list of options supported by allinput plugins.
The xmpp server to connect to. This is optional. If you omit this setting,the host on the user/identity is used. (foo.com
for user@foo.com
)
The xmpp password for the user/identity.
if muc/multi-user-chat required, give the name of the room thatyou want to join: room@conference.domain/nick
The user or resource ID, like foo@example.com
.
The following configuration options are supported by all input plugins:
"plain"
The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.
true
Disable or enable metric logging for this specific plugin instanceby 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 xmpp inputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
input { xmpp { id => "my_plugin_id" }}
Add any number of arbitrary tags to your event.
This can help with processing later.
Add a type
field to all events handled by this input.
Types are used mainly for filter activation.
The type is stored as part of the event itself, so you canalso use the type to search for it in Kibana.
If you try to set a type on an event that already has one (forexample when you send an event from a shipper to an indexer) thena new input will not override the existing type. A type set atthe shipper stays with that event for its life evenwhen sent to another Logstash server.