Jms input pluginedit

  • Plugin version: v3.0.2
  • Released on: 2017-06-23
  • Changelog

Getting Helpedit

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.

Descriptionedit

Read events from a Jms Broker. Supports both Jms Queues and Topics.

For more information about Jms, see http://docs.oracle.com/javaee/6/tutorial/doc/bncdq.html For more information about the Ruby Gem used, see http://github.com/reidmorrison/jruby-jms Here is a config example to pull from a queue: jms { include_header ⇒ false include_properties ⇒ false include_body ⇒ true use_jms_timestamp ⇒ false interval ⇒ 10 destination ⇒ "myqueue" pub-sub ⇒ false yaml_file ⇒ "~/jms.yml" yaml_section ⇒ "mybroker" }

Jms Input Configuration Optionsedit

This plugin supports the following configuration options plus the Common Options described later.

Also see Common Options for a list of options supported by all input plugins.

 

broker_urledit

  • Value type is string
  • There is no default value for this setting.

Url to use when connecting to the JMS provider

destinationedit

  • This is a required setting.
  • Value type is string
  • There is no default value for this setting.

Name of the destination queue or topic to use.

factoryedit

  • Value type is string
  • There is no default value for this setting.

Name of JMS Provider Factory class

include_bodyedit

  • Value type is boolean
  • Default value is true

Include JMS Message Body in the event Supports TextMessage, MapMessage and ByteMessage If the JMS Message is a TextMessage or ByteMessage, then the value will be in the "message" field of the event If the JMS Message is a MapMessage, then all the key/value pairs will be added in the Hashmap of the event StreamMessage and ObjectMessage are not supported

include_headeredit

  • Value type is boolean
  • Default value is true

A JMS message has three parts : Message Headers (required) Message Properties (optional) Message Bodies (optional) You can tell the input plugin which parts should be included in the event produced by Logstash

Include JMS Message Header Field values in the event

include_propertiesedit

  • Value type is boolean
  • Default value is true

Include JMS Message Properties Field values in the event

intervaledit

  • Value type is number
  • Default value is 10

Polling interval in seconds. This is the time sleeping between asks to a consumed Queue. This parameter has non influence in the case of a subcribed Topic.

jndi_contextedit

  • Value type is hash
  • There is no default value for this setting.

Mandatory if jndi lookup is being used, contains details on how to connect to JNDI server

jndi_nameedit

  • Value type is string
  • There is no default value for this setting.

Name of JNDI entry at which the Factory can be found

passwordedit

  • Value type is string
  • There is no default value for this setting.

Password to use when connecting to the JMS provider

pub_subedit

  • Value type is boolean
  • Default value is false

If pub-sub (topic) style should be used.

require_jarsedit

  • Value type is array
  • There is no default value for this setting.

If you do not use an yaml configuration use either the factory or jndi_name. An optional array of Jar file names to load for the specified JMS provider. By using this option it is not necessary to put all the JMS Provider specific jar files into the java CLASSPATH prior to starting Logstash.

runneredit

  • Value can be any of: consumer, async, thread
  • Default value is "consumer"

Choose an implementation of the run block. Value can be either consumer, async or thread

selectoredit

  • Value type is string
  • There is no default value for this setting.

Set the selector to use to get messages off the queue or topic

threadsedit

  • Value type is number
  • Default value is 1

timeoutedit

  • Value type is number
  • Default value is 60

Initial connection timeout in seconds.

use_jms_timestampedit

  • Value type is boolean
  • Default value is false

Convert the JMSTimestamp header field to the @timestamp value of the event

usernameedit

  • Value type is string
  • There is no default value for this setting.

Username to connect to JMS provider with

yaml_fileedit

  • Value type is string
  • There is no default value for this setting.

Yaml config file

yaml_sectionedit

  • Value type is string
  • There is no default value for this setting.

Yaml config file section name For some known examples, see: [Example jms.yml](https://github.com/reidmorrison/jruby-jms/blob/master/examples/jms.yml)

Common Optionsedit

The following configuration options are supported by all input plugins:

Detailsedit

 

add_fieldedit

  • Value type is hash
  • Default value is {}

Add a field to an event

codecedit

  • Value type is codec
  • Default value is "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.

enable_metricedit

  • 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.

  • Value type is string
  • There is no default value for this setting.

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 useful when you have two or more plugins of the same type, for example, if you have 2 grok filters. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

output {
 stdout {
   id => "my_plugin_id"
 }
}

tagsedit

  • Value type is array
  • There is no default value for this setting.

Add any number of arbitrary tags to your event.

This can help with processing later.

typeedit

  • Value type is string
  • There is no default value for this setting.

This is the base class for Logstash inputs. 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 can also use the type to search for it in Kibana.

If you try to set a type on an event that already has one (for example when you send an event from a shipper to an indexer) then a new input will not override the existing type. A type set at the shipper stays with that event for its life even when sent to another Logstash server.