Jms output plugin v3.0.3

  • Plugin version: v3.0.3
  • Released on: 2018-04-06
  • Changelog

For other versions, see the overview list.

To learn more about Logstash, see the Logstash Reference.

Getting Help

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.

Description

Write events to 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 : jms { include_header ⇒ false include_properties ⇒ false include_body ⇒ true use_jms_timestamp ⇒ false queue_name ⇒ "myqueue" yaml_file ⇒ "~/jms.yml" yaml_section ⇒ "mybroker" }

Jms Output Configuration Options

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 output plugins.

 

broker_url

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

Url to use when connecting to the JMS provider

delivery_mode

  • Value type is string
  • Default value is nil

Name of delivery mode to use Options are "persistent" and "non_persistent" if not defined nothing will be passed.

destination

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

Name of the destination queue or topic to use. Mandatory

factory

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

Name of JMS Provider Factory class

jndi_context

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

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

Name of JNDI entry at which the Factory can be found

password

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

Password to use when connecting to the JMS provider

pub_sub

  • Value type is boolean
  • Default value is false

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

require_jars

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

username

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

Username to connect to JMS provider with

yaml_file

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

Yaml config file

yaml_section

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

The following configuration options are supported by all output plugins:

Setting Input typeRequired

codec

codec

No

enable_metric

boolean

No

id

string

No

codec

  • 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

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

id

  • 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 jms outputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

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