Rackspace input plugin v3.0.4

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

For other versions, see the overview list.

To learn more about Logstash, see the Logstash Reference.

Getting help

edit

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

edit

Receives events from a Rackspace Cloud Queue service.

Rackspace Input Configuration Options

edit

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

Setting Input type Required

api_key

string

Yes

claim

number

No

queue

string

No

region

string

No

ttl

number

No

username

string

Yes

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

 

api_key

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

Rackspace Cloud API Key

claim

edit
  • Value type is number
  • Default value is 1

number of messages to claim Min: 1, Max: 10

queue

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

Rackspace Queue Name

region

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

Rackspace region ord, dfw, lon, syd, etc

ttl

edit
  • Value type is number
  • Default value is 60

length of time to hold claim Min: 60

username

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

Rackspace Cloud Username

Common options

edit

These configuration options are supported by all input plugins:

Setting Input type Required

add_field

hash

No

codec

codec

No

enable_metric

boolean

No

id

string

No

tags

array

No

type

string

No

add_field

edit
  • Value type is hash
  • Default value is {}

Add a field to an event

codec

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

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

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

tags

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

type

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

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.