Rackspace output plugin v2.0.7edit

  • Plugin version: v2.0.7
  • Released on: 2017-08-16
  • Changelog

For other versions, see the overview list.

To learn more about Logstash, see the Logstash Reference.

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

Sends events to a Rackspace Cloud Queue service.

Rackspace Output Configuration Optionsedit

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

Setting Input type Required

api_key

string

Yes

queue

string

No

region

string

No

ttl

number

No

username

string

Yes

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

 

api_keyedit

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

Rackspace Cloud API Key

queueedit

  • Value type is string
  • Default value is "logstash"

Rackspace Queue Name

regionedit

  • Value type is string
  • Default value is "dfw"

Rackspace region ord, dfw, lon, syd, etc

ttledit

  • Value type is number
  • Default value is 360

time for item to live in queue

usernameedit

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

Rackspace Cloud Username

Common Optionsedit

The following configuration options are supported by all output plugins:

Setting Input type Required

enable_metric

boolean

No

id

string

No

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.

idedit

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

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