logstash-integration-rabbitmq 7.0.0-java
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/CHANGELOG.md +9 -0
- data/CONTRIBUTORS +27 -0
- data/Gemfile +11 -0
- data/LICENSE +13 -0
- data/NOTICE.TXT +5 -0
- data/README.md +98 -0
- data/docs/index.asciidoc +29 -0
- data/docs/input-rabbitmq.asciidoc +398 -0
- data/docs/output-rabbitmq.asciidoc +272 -0
- data/lib/logstash/inputs/rabbitmq.rb +317 -0
- data/lib/logstash/outputs/rabbitmq.rb +131 -0
- data/lib/logstash/plugin_mixins/rabbitmq_connection.rb +234 -0
- data/lib/logstash_registry.rb +7 -0
- data/logstash-integration-rabbitmq.gemspec +53 -0
- data/spec/fixtures/README.md +150 -0
- data/spec/fixtures/client/cert.pem +69 -0
- data/spec/fixtures/client/key.pem +27 -0
- data/spec/fixtures/client/keycert.p12 +0 -0
- data/spec/fixtures/client/req.pem +15 -0
- data/spec/fixtures/client_untrusted/cert.pem +19 -0
- data/spec/fixtures/client_untrusted/key.pem +28 -0
- data/spec/fixtures/client_untrusted/keycert.p12 +0 -0
- data/spec/fixtures/server/cert.pem +69 -0
- data/spec/fixtures/server/key.pem +27 -0
- data/spec/fixtures/server/key_password +1 -0
- data/spec/fixtures/server/keycert.p12 +0 -0
- data/spec/fixtures/server/rabbitmq.config +10 -0
- data/spec/fixtures/server/req.pem +15 -0
- data/spec/fixtures/testca/cacert.cer +0 -0
- data/spec/fixtures/testca/cacert.pem +17 -0
- data/spec/fixtures/testca/certs/01.pem +18 -0
- data/spec/fixtures/testca/certs/02.pem +18 -0
- data/spec/fixtures/testca/certs/05.pem +69 -0
- data/spec/fixtures/testca/certs/06.pem +69 -0
- data/spec/fixtures/testca/index.txt +4 -0
- data/spec/fixtures/testca/index.txt.attr +1 -0
- data/spec/fixtures/testca/index.txt.attr.old +1 -0
- data/spec/fixtures/testca/index.txt.old +3 -0
- data/spec/fixtures/testca/openssl.cnf +53 -0
- data/spec/fixtures/testca/private/cakey.pem +27 -0
- data/spec/fixtures/testca/serial +1 -0
- data/spec/fixtures/testca/serial.old +1 -0
- data/spec/inputs/rabbitmq_spec.rb +279 -0
- data/spec/outputs/rabbitmq_spec.rb +232 -0
- data/spec/plugin_mixins/rabbitmq_connection_spec.rb +175 -0
- metadata +256 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: a6bbe63689bc0b3dcdb01d9bad482e1425a77805e793873b4b4739db79e49144
|
4
|
+
data.tar.gz: 2e8b2111e92926ae9d5f5fc857289509909b4d1f02ca9dc2df3463830c9226dc
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 3d7efe8f934f4b234f5ccfccbc3c206a4dbc04a0351b7d4e7541c236fb5cebb043d9bffb2f59acefcb7f4d383bb56d2d5863251ca3fedb8e10e2a4da715eb40d
|
7
|
+
data.tar.gz: fa953afe5684037dc67dfbdf1a1319fa0d7bf8ea622078a0be6e18af3e0f04755c3fe12a59d4d6d59f69dde8d3e919e59e235d565da7d87e15a476083d786a6e
|
data/CHANGELOG.md
ADDED
@@ -0,0 +1,9 @@
|
|
1
|
+
## 7.0.0
|
2
|
+
- Initial release of the RabbitMQ Integration Plugin, which combines
|
3
|
+
previously-separate RabbitMQ plugins and shared dependencies into a single
|
4
|
+
codebase; independent changelogs for previous versions can be found:
|
5
|
+
- [RabbitMQ Input Plugin @6.0.3](https://github.com/logstash-plugins/logstash-input-rabbitmq/blob/v6.0.3/CHANGELOG.md)
|
6
|
+
- [RabbitMQ Output Plugin @5.1.1](https://github.com/logstash-plugins/logstash-output-rabbitmq/blob/v5.1.1/CHANGELOG.md)
|
7
|
+
- Absorbed connection mixin dependency; independent changelog history for
|
8
|
+
the mixin can be found here: [RabbitMQ Connection Mixin @5.1.0](https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/blob/v5.1.0/CHANGELOG.md)
|
9
|
+
- In the Output plugin, when a connection is flagged as blocked, back-pressure is now propagated to the pipeline until the connection is either unblocked or recovered, preventing runaway writes to blocked connections ([#1](https://github.com/logstash-plugins/logstash-integration-rabbitmq/pull/1))
|
data/CONTRIBUTORS
ADDED
@@ -0,0 +1,27 @@
|
|
1
|
+
The following is a list of people who have contributed ideas, code, bug
|
2
|
+
reports, or in general have helped logstash along its way.
|
3
|
+
|
4
|
+
Contributors:
|
5
|
+
* Avishai Ish-Shalom (avishai-ish-shalom)
|
6
|
+
* Colin Surprenant (colinsurprenant)
|
7
|
+
* Jonathan Van Eenwyk (jdve)
|
8
|
+
* Jordan Sissel (jordansissel)
|
9
|
+
* João Duarte (jsvd)
|
10
|
+
* Mathieu MILLET (htam-net)
|
11
|
+
* Michael Klishin (michaelklishin)
|
12
|
+
* Michael Zaccari (mzaccari)
|
13
|
+
* Nick Ethier (nickethier)
|
14
|
+
* Pier-Hugues Pellerin (ph)
|
15
|
+
* Richard Pijnenburg (electrical)
|
16
|
+
* Suyog Rao (suyograo)
|
17
|
+
* Tim Potter (tpot)
|
18
|
+
* Avleen Vig (avleen)
|
19
|
+
* Kurt Hurtado (kurtado)
|
20
|
+
* Marc Fournier (mfournier)
|
21
|
+
* Sebastian Schmelzer (ssc-)
|
22
|
+
* Ry Biesemeyer (yaauie)
|
23
|
+
|
24
|
+
Note: If you've sent us patches, bug reports, or otherwise contributed to
|
25
|
+
Logstash, and you aren't on the list above and want to be, please let us know
|
26
|
+
and we'll make sure you're here. Contributions from folks like you are what make
|
27
|
+
open source awesome.
|
data/Gemfile
ADDED
@@ -0,0 +1,11 @@
|
|
1
|
+
source 'https://rubygems.org'
|
2
|
+
|
3
|
+
gemspec
|
4
|
+
|
5
|
+
logstash_path = ENV["LOGSTASH_PATH"] || "../../logstash"
|
6
|
+
use_logstash_source = ENV["LOGSTASH_SOURCE"] && ENV["LOGSTASH_SOURCE"].to_s == "1"
|
7
|
+
|
8
|
+
if Dir.exist?(logstash_path) && use_logstash_source
|
9
|
+
gem 'logstash-core', :path => "#{logstash_path}/logstash-core"
|
10
|
+
gem 'logstash-core-plugin-api', :path => "#{logstash_path}/logstash-core-plugin-api"
|
11
|
+
end
|
data/LICENSE
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
Copyright (c) 2012-2018 Elasticsearch <http://www.elastic.co>
|
2
|
+
|
3
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
you may not use this file except in compliance with the License.
|
5
|
+
You may obtain a copy of the License at
|
6
|
+
|
7
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
|
9
|
+
Unless required by applicable law or agreed to in writing, software
|
10
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
See the License for the specific language governing permissions and
|
13
|
+
limitations under the License.
|
data/NOTICE.TXT
ADDED
data/README.md
ADDED
@@ -0,0 +1,98 @@
|
|
1
|
+
# Logstash Plugin
|
2
|
+
|
3
|
+
[![Travis Build Status](https://travis-ci.org/logstash-plugins/logstash-integration-rabbitmq.svg)](https://travis-ci.org/logstash-plugins/logstash-integration-rabbitmq)
|
4
|
+
|
5
|
+
This is a plugin for [Logstash](https://github.com/elastic/logstash).
|
6
|
+
|
7
|
+
It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
|
8
|
+
|
9
|
+
## Documentation
|
10
|
+
|
11
|
+
Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one [central location](http://www.elastic.co/guide/en/logstash/current/).
|
12
|
+
|
13
|
+
- For formatting code or config example, you can use the asciidoc `[source,ruby]` directive
|
14
|
+
- For more asciidoc formatting tips, see the excellent reference here https://github.com/elastic/docs#asciidoc-guide
|
15
|
+
|
16
|
+
## Need Help?
|
17
|
+
|
18
|
+
Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.
|
19
|
+
|
20
|
+
## Developing
|
21
|
+
|
22
|
+
### 1. Plugin Developement and Testing
|
23
|
+
|
24
|
+
#### Code
|
25
|
+
- To get started, you'll need JRuby with the Bundler gem installed.
|
26
|
+
|
27
|
+
- Create a new plugin or clone and existing from the GitHub [logstash-plugins](https://github.com/logstash-plugins) organization. We also provide [example plugins](https://github.com/logstash-plugins?query=example).
|
28
|
+
|
29
|
+
- Install dependencies
|
30
|
+
```sh
|
31
|
+
bundle install
|
32
|
+
```
|
33
|
+
|
34
|
+
#### Test
|
35
|
+
|
36
|
+
- Update your dependencies
|
37
|
+
|
38
|
+
```sh
|
39
|
+
bundle install
|
40
|
+
```
|
41
|
+
|
42
|
+
- Run tests
|
43
|
+
|
44
|
+
```sh
|
45
|
+
bundle exec rspec
|
46
|
+
```
|
47
|
+
|
48
|
+
### 2. Running your unpublished Plugin in Logstash
|
49
|
+
|
50
|
+
#### 2.1 Run in a local Logstash clone
|
51
|
+
|
52
|
+
- Edit Logstash `Gemfile` and add the local plugin path, for example:
|
53
|
+
```ruby
|
54
|
+
gem "logstash-filter-awesome", :path => "/your/local/logstash-filter-awesome"
|
55
|
+
```
|
56
|
+
- Install plugin
|
57
|
+
```sh
|
58
|
+
# Logstash 2.3 and higher
|
59
|
+
bin/logstash-plugin install --no-verify
|
60
|
+
|
61
|
+
# Prior to Logstash 2.3
|
62
|
+
bin/plugin install --no-verify
|
63
|
+
|
64
|
+
```
|
65
|
+
- Run Logstash with your plugin
|
66
|
+
```sh
|
67
|
+
bin/logstash -e 'filter {awesome {}}'
|
68
|
+
```
|
69
|
+
At this point any modifications to the plugin code will be applied to this local Logstash setup. After modifying the plugin, simply rerun Logstash.
|
70
|
+
|
71
|
+
#### 2.2 Run in an installed Logstash
|
72
|
+
|
73
|
+
You can use the same **2.1** method to run your plugin in an installed Logstash by editing its `Gemfile` and pointing the `:path` to your local plugin development directory or you can build the gem and install it using:
|
74
|
+
|
75
|
+
- Build your plugin gem
|
76
|
+
```sh
|
77
|
+
gem build logstash-filter-awesome.gemspec
|
78
|
+
```
|
79
|
+
- Install the plugin from the Logstash home
|
80
|
+
```sh
|
81
|
+
# Logstash 2.3 and higher
|
82
|
+
bin/logstash-plugin install --no-verify
|
83
|
+
|
84
|
+
# Prior to Logstash 2.3
|
85
|
+
bin/plugin install --no-verify
|
86
|
+
|
87
|
+
```
|
88
|
+
- Start Logstash and proceed to test the plugin
|
89
|
+
|
90
|
+
## Contributing
|
91
|
+
|
92
|
+
All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.
|
93
|
+
|
94
|
+
Programming is not a required skill. Whatever you've seen about open source and maintainers or community members saying "send patches or die" - you will not see that here.
|
95
|
+
|
96
|
+
It is more important to the community that you are able to contribute.
|
97
|
+
|
98
|
+
For more information about contributing, see the [CONTRIBUTING](https://github.com/elastic/logstash/blob/master/CONTRIBUTING.md) file.
|
data/docs/index.asciidoc
ADDED
@@ -0,0 +1,29 @@
|
|
1
|
+
:plugin: rabbitmq
|
2
|
+
:type: integration
|
3
|
+
:no_codec:
|
4
|
+
|
5
|
+
///////////////////////////////////////////
|
6
|
+
START - GENERATED VARIABLES, DO NOT EDIT!
|
7
|
+
///////////////////////////////////////////
|
8
|
+
:version: %VERSION%
|
9
|
+
:release_date: %RELEASE_DATE%
|
10
|
+
:changelog_url: %CHANGELOG_URL%
|
11
|
+
:include_path: ../../../../logstash/docs/include
|
12
|
+
///////////////////////////////////////////
|
13
|
+
END - GENERATED VARIABLES, DO NOT EDIT!
|
14
|
+
///////////////////////////////////////////
|
15
|
+
|
16
|
+
[id="plugins-{type}s-{plugin}"]
|
17
|
+
|
18
|
+
=== Rabbitmq Integration Plugin
|
19
|
+
|
20
|
+
include::{include_path}/plugin_header.asciidoc[]
|
21
|
+
|
22
|
+
==== Description
|
23
|
+
|
24
|
+
The RabbitMQ Integration Plugin provides integrated plugins for working with http://www.rabbitmq.com/[RabbitMQ].
|
25
|
+
|
26
|
+
- {logstash-ref}/plugins-inputs-rabbitmq.html[RabbitMQ Input Plugin]
|
27
|
+
- {logstash-ref}/plugins-outputs-rabbitmq.html[RabbitMQ Output Plugin]
|
28
|
+
|
29
|
+
:no_codec!:
|
@@ -0,0 +1,398 @@
|
|
1
|
+
:plugin: rabbitmq
|
2
|
+
:type: input
|
3
|
+
:default_codec: json
|
4
|
+
|
5
|
+
///////////////////////////////////////////
|
6
|
+
START - GENERATED VARIABLES, DO NOT EDIT!
|
7
|
+
///////////////////////////////////////////
|
8
|
+
:version: %VERSION%
|
9
|
+
:release_date: %RELEASE_DATE%
|
10
|
+
:changelog_url: %CHANGELOG_URL%
|
11
|
+
:include_path: ../../../../logstash/docs/include
|
12
|
+
///////////////////////////////////////////
|
13
|
+
END - GENERATED VARIABLES, DO NOT EDIT!
|
14
|
+
///////////////////////////////////////////
|
15
|
+
|
16
|
+
[id="plugins-{type}s-{plugin}"]
|
17
|
+
|
18
|
+
=== Rabbitmq input plugin
|
19
|
+
|
20
|
+
include::{include_path}/plugin_header.asciidoc[]
|
21
|
+
|
22
|
+
==== Description
|
23
|
+
|
24
|
+
Pull events from a http://www.rabbitmq.com/[RabbitMQ] queue.
|
25
|
+
|
26
|
+
The default settings will create an entirely transient queue and listen for all messages by default.
|
27
|
+
If you need durability or any other advanced settings, please set the appropriate options
|
28
|
+
|
29
|
+
This plugin uses the http://rubymarchhare.info/[March Hare] library
|
30
|
+
for interacting with the RabbitMQ server. Most configuration options
|
31
|
+
map directly to standard RabbitMQ and AMQP concepts. The
|
32
|
+
https://www.rabbitmq.com/amqp-0-9-1-reference.html[AMQP 0-9-1 reference guide]
|
33
|
+
and other parts of the RabbitMQ documentation are useful for deeper
|
34
|
+
understanding.
|
35
|
+
|
36
|
+
The properties of messages received will be stored in the
|
37
|
+
`[@metadata][rabbitmq_properties]` field if the `@metadata_enabled` setting is checked.
|
38
|
+
Note that storing metadata may degrade performance.
|
39
|
+
The following properties may be available (in most cases dependent on whether
|
40
|
+
they were set by the sender):
|
41
|
+
|
42
|
+
* app-id
|
43
|
+
* cluster-id
|
44
|
+
* consumer-tag
|
45
|
+
* content-encoding
|
46
|
+
* content-type
|
47
|
+
* correlation-id
|
48
|
+
* delivery-mode
|
49
|
+
* exchange
|
50
|
+
* expiration
|
51
|
+
* message-id
|
52
|
+
* priority
|
53
|
+
* redeliver
|
54
|
+
* reply-to
|
55
|
+
* routing-key
|
56
|
+
* timestamp
|
57
|
+
* type
|
58
|
+
* user-id
|
59
|
+
|
60
|
+
For example, to get the RabbitMQ message's timestamp property
|
61
|
+
into the Logstash event's `@timestamp` field, use the date
|
62
|
+
filter to parse the `[@metadata][rabbitmq_properties][timestamp]`
|
63
|
+
field:
|
64
|
+
[source,ruby]
|
65
|
+
filter {
|
66
|
+
if [@metadata][rabbitmq_properties][timestamp] {
|
67
|
+
date {
|
68
|
+
match => ["[@metadata][rabbitmq_properties][timestamp]", "UNIX"]
|
69
|
+
}
|
70
|
+
}
|
71
|
+
}
|
72
|
+
|
73
|
+
Additionally, any message headers will be saved in the
|
74
|
+
`[@metadata][rabbitmq_headers]` field.
|
75
|
+
|
76
|
+
[id="plugins-{type}s-{plugin}-options"]
|
77
|
+
==== Rabbitmq Input Configuration Options
|
78
|
+
|
79
|
+
This plugin supports the following configuration options plus the <<plugins-{type}s-{plugin}-common-options>> described later.
|
80
|
+
|
81
|
+
[cols="<,<,<",options="header",]
|
82
|
+
|=======================================================================
|
83
|
+
|Setting |Input type|Required
|
84
|
+
| <<plugins-{type}s-{plugin}-ack>> |<<boolean,boolean>>|No
|
85
|
+
| <<plugins-{type}s-{plugin}-arguments>> |<<array,array>>|No
|
86
|
+
| <<plugins-{type}s-{plugin}-auto_delete>> |<<boolean,boolean>>|No
|
87
|
+
| <<plugins-{type}s-{plugin}-automatic_recovery>> |<<boolean,boolean>>|No
|
88
|
+
| <<plugins-{type}s-{plugin}-connect_retry_interval>> |<<number,number>>|No
|
89
|
+
| <<plugins-{type}s-{plugin}-connection_timeout>> |<<number,number>>|No
|
90
|
+
| <<plugins-{type}s-{plugin}-durable>> |<<boolean,boolean>>|No
|
91
|
+
| <<plugins-{type}s-{plugin}-exchange>> |<<string,string>>|No
|
92
|
+
| <<plugins-{type}s-{plugin}-exchange_type>> |<<string,string>>|No
|
93
|
+
| <<plugins-{type}s-{plugin}-exclusive>> |<<boolean,boolean>>|No
|
94
|
+
| <<plugins-{type}s-{plugin}-heartbeat>> |<<number,number>>|No
|
95
|
+
| <<plugins-{type}s-{plugin}-host>> |<<string,string>>|Yes
|
96
|
+
| <<plugins-{type}s-{plugin}-key>> |<<string,string>>|No
|
97
|
+
| <<plugins-{type}s-{plugin}-metadata_enabled>> |<<boolean,boolean>>|No
|
98
|
+
| <<plugins-{type}s-{plugin}-passive>> |<<boolean,boolean>>|No
|
99
|
+
| <<plugins-{type}s-{plugin}-password>> |<<password,password>>|No
|
100
|
+
| <<plugins-{type}s-{plugin}-port>> |<<number,number>>|No
|
101
|
+
| <<plugins-{type}s-{plugin}-prefetch_count>> |<<number,number>>|No
|
102
|
+
| <<plugins-{type}s-{plugin}-queue>> |<<string,string>>|No
|
103
|
+
| <<plugins-{type}s-{plugin}-ssl>> |<<boolean,boolean>>|No
|
104
|
+
| <<plugins-{type}s-{plugin}-ssl_certificate_password>> |<<string,string>>|No
|
105
|
+
| <<plugins-{type}s-{plugin}-ssl_certificate_path>> |a valid filesystem path|No
|
106
|
+
| <<plugins-{type}s-{plugin}-ssl_version>> |<<string,string>>|No
|
107
|
+
| <<plugins-{type}s-{plugin}-subscription_retry_interval_seconds>> |<<number,number>>|Yes
|
108
|
+
| <<plugins-{type}s-{plugin}-threads>> |<<number,number>>|No
|
109
|
+
| <<plugins-{type}s-{plugin}-user>> |<<string,string>>|No
|
110
|
+
| <<plugins-{type}s-{plugin}-vhost>> |<<string,string>>|No
|
111
|
+
|=======================================================================
|
112
|
+
|
113
|
+
Also see <<plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
|
114
|
+
input plugins.
|
115
|
+
|
116
|
+
|
117
|
+
|
118
|
+
[id="plugins-{type}s-{plugin}-ack"]
|
119
|
+
===== `ack`
|
120
|
+
|
121
|
+
* Value type is <<boolean,boolean>>
|
122
|
+
* Default value is `true`
|
123
|
+
|
124
|
+
Enable message acknowledgements. With acknowledgements
|
125
|
+
messages fetched by Logstash but not yet sent into the
|
126
|
+
Logstash pipeline will be requeued by the server if Logstash
|
127
|
+
shuts down. Acknowledgements will however hurt the message
|
128
|
+
throughput.
|
129
|
+
|
130
|
+
This will only send an ack back every `prefetch_count` messages.
|
131
|
+
Working in batches provides a performance boost here.
|
132
|
+
|
133
|
+
[id="plugins-{type}s-{plugin}-arguments"]
|
134
|
+
===== `arguments`
|
135
|
+
|
136
|
+
* Value type is <<array,array>>
|
137
|
+
* Default value is `{}`
|
138
|
+
|
139
|
+
Extra queue arguments as an array.
|
140
|
+
To make a RabbitMQ queue mirrored, use: `{"x-ha-policy" => "all"}`
|
141
|
+
|
142
|
+
[id="plugins-{type}s-{plugin}-auto_delete"]
|
143
|
+
===== `auto_delete`
|
144
|
+
|
145
|
+
* Value type is <<boolean,boolean>>
|
146
|
+
* Default value is `false`
|
147
|
+
|
148
|
+
Should the queue be deleted on the broker when the last consumer
|
149
|
+
disconnects? Set this option to `false` if you want the queue to remain
|
150
|
+
on the broker, queueing up messages until a consumer comes along to
|
151
|
+
consume them.
|
152
|
+
|
153
|
+
[id="plugins-{type}s-{plugin}-automatic_recovery"]
|
154
|
+
===== `automatic_recovery`
|
155
|
+
|
156
|
+
* Value type is <<boolean,boolean>>
|
157
|
+
* Default value is `true`
|
158
|
+
|
159
|
+
Set this to automatically recover from a broken connection. You almost certainly don't want to override this!!!
|
160
|
+
|
161
|
+
[id="plugins-{type}s-{plugin}-connect_retry_interval"]
|
162
|
+
===== `connect_retry_interval`
|
163
|
+
|
164
|
+
* Value type is <<number,number>>
|
165
|
+
* Default value is `1`
|
166
|
+
|
167
|
+
Time in seconds to wait before retrying a connection
|
168
|
+
|
169
|
+
[id="plugins-{type}s-{plugin}-connection_timeout"]
|
170
|
+
===== `connection_timeout`
|
171
|
+
|
172
|
+
* Value type is <<number,number>>
|
173
|
+
* There is no default value for this setting.
|
174
|
+
|
175
|
+
The default connection timeout in milliseconds. If not specified the timeout is infinite.
|
176
|
+
|
177
|
+
[id="plugins-{type}s-{plugin}-durable"]
|
178
|
+
===== `durable`
|
179
|
+
|
180
|
+
* Value type is <<boolean,boolean>>
|
181
|
+
* Default value is `false`
|
182
|
+
|
183
|
+
Is this queue durable? (aka; Should it survive a broker restart?)
|
184
|
+
|
185
|
+
[id="plugins-{type}s-{plugin}-exchange"]
|
186
|
+
===== `exchange`
|
187
|
+
|
188
|
+
* Value type is <<string,string>>
|
189
|
+
* There is no default value for this setting.
|
190
|
+
|
191
|
+
The name of the exchange to bind the queue to. Specify `exchange_type`
|
192
|
+
as well to declare the exchange if it does not exist
|
193
|
+
|
194
|
+
[id="plugins-{type}s-{plugin}-exchange_type"]
|
195
|
+
===== `exchange_type`
|
196
|
+
|
197
|
+
* Value type is <<string,string>>
|
198
|
+
* There is no default value for this setting.
|
199
|
+
|
200
|
+
The type of the exchange to bind to. Specifying this will cause this plugin
|
201
|
+
to declare the exchange if it does not exist.
|
202
|
+
|
203
|
+
[id="plugins-{type}s-{plugin}-exclusive"]
|
204
|
+
===== `exclusive`
|
205
|
+
|
206
|
+
* Value type is <<boolean,boolean>>
|
207
|
+
* Default value is `false`
|
208
|
+
|
209
|
+
Is the queue exclusive? Exclusive queues can only be used by the connection
|
210
|
+
that declared them and will be deleted when it is closed (e.g. due to a Logstash
|
211
|
+
restart).
|
212
|
+
|
213
|
+
[id="plugins-{type}s-{plugin}-heartbeat"]
|
214
|
+
===== `heartbeat`
|
215
|
+
|
216
|
+
* Value type is <<number,number>>
|
217
|
+
* There is no default value for this setting.
|
218
|
+
|
219
|
+
Heartbeat delay in seconds. If unspecified no heartbeats will be sent
|
220
|
+
|
221
|
+
[id="plugins-{type}s-{plugin}-host"]
|
222
|
+
===== `host`
|
223
|
+
|
224
|
+
* This is a required setting.
|
225
|
+
* Value type is <<string,string>>
|
226
|
+
* There is no default value for this setting.
|
227
|
+
|
228
|
+
Common functionality for the rabbitmq input/output
|
229
|
+
RabbitMQ server address(es)
|
230
|
+
host can either be a single host, or a list of hosts
|
231
|
+
i.e.
|
232
|
+
host => "localhost"
|
233
|
+
or
|
234
|
+
host => ["host01", "host02]
|
235
|
+
|
236
|
+
if multiple hosts are provided on the initial connection and any subsequent
|
237
|
+
recovery attempts of the hosts is chosen at random and connected to.
|
238
|
+
Note that only one host connection is active at a time.
|
239
|
+
|
240
|
+
[id="plugins-{type}s-{plugin}-key"]
|
241
|
+
===== `key`
|
242
|
+
|
243
|
+
* Value type is <<string,string>>
|
244
|
+
* Default value is `"logstash"`
|
245
|
+
|
246
|
+
The routing key to use when binding a queue to the exchange.
|
247
|
+
This is only relevant for direct or topic exchanges.
|
248
|
+
|
249
|
+
* Routing keys are ignored on fanout exchanges.
|
250
|
+
* Wildcards are not valid on direct exchanges.
|
251
|
+
|
252
|
+
[id="plugins-{type}s-{plugin}-metadata_enabled"]
|
253
|
+
===== `metadata_enabled`
|
254
|
+
|
255
|
+
* Value type is <<boolean,boolean>>
|
256
|
+
* Default value is `false`
|
257
|
+
|
258
|
+
Enable the storage of message headers and properties in `@metadata`. This may impact performance
|
259
|
+
|
260
|
+
[id="plugins-{type}s-{plugin}-passive"]
|
261
|
+
===== `passive`
|
262
|
+
|
263
|
+
* Value type is <<boolean,boolean>>
|
264
|
+
* Default value is `false`
|
265
|
+
|
266
|
+
If true the queue will be passively declared, meaning it must
|
267
|
+
already exist on the server. To have Logstash create the queue
|
268
|
+
if necessary leave this option as false. If actively declaring
|
269
|
+
a queue that already exists, the queue options for this plugin
|
270
|
+
(durable etc) must match those of the existing queue.
|
271
|
+
|
272
|
+
[id="plugins-{type}s-{plugin}-password"]
|
273
|
+
===== `password`
|
274
|
+
|
275
|
+
* Value type is <<password,password>>
|
276
|
+
* Default value is `"guest"`
|
277
|
+
|
278
|
+
RabbitMQ password
|
279
|
+
|
280
|
+
[id="plugins-{type}s-{plugin}-port"]
|
281
|
+
===== `port`
|
282
|
+
|
283
|
+
* Value type is <<number,number>>
|
284
|
+
* Default value is `5672`
|
285
|
+
|
286
|
+
RabbitMQ port to connect on
|
287
|
+
|
288
|
+
[id="plugins-{type}s-{plugin}-prefetch_count"]
|
289
|
+
===== `prefetch_count`
|
290
|
+
|
291
|
+
* Value type is <<number,number>>
|
292
|
+
* Default value is `256`
|
293
|
+
|
294
|
+
Prefetch count. If acknowledgements are enabled with the `ack`
|
295
|
+
option, specifies the number of outstanding unacknowledged
|
296
|
+
messages allowed.
|
297
|
+
|
298
|
+
[id="plugins-{type}s-{plugin}-queue"]
|
299
|
+
===== `queue`
|
300
|
+
|
301
|
+
* Value type is <<string,string>>
|
302
|
+
* Default value is `""`
|
303
|
+
|
304
|
+
The properties to extract from each message and store in a
|
305
|
+
@metadata field.
|
306
|
+
|
307
|
+
Technically the exchange, redeliver, and routing-key
|
308
|
+
properties belong to the envelope and not the message but we
|
309
|
+
ignore that distinction here. However, we extract the
|
310
|
+
headers separately via get_headers even though the header
|
311
|
+
table technically is a message property.
|
312
|
+
|
313
|
+
Freezing all strings so that code modifying the event's
|
314
|
+
@metadata field can't touch them.
|
315
|
+
|
316
|
+
If updating this list, remember to update the documentation
|
317
|
+
above too.
|
318
|
+
The default codec for this plugin is JSON. You can override this to suit your particular needs however.
|
319
|
+
The name of the queue Logstash will consume events from. If
|
320
|
+
left empty, a transient queue with an randomly chosen name
|
321
|
+
will be created.
|
322
|
+
|
323
|
+
[id="plugins-{type}s-{plugin}-ssl"]
|
324
|
+
===== `ssl`
|
325
|
+
|
326
|
+
* Value type is <<boolean,boolean>>
|
327
|
+
* There is no default value for this setting.
|
328
|
+
|
329
|
+
Enable or disable SSL.
|
330
|
+
Note that by default remote certificate verification is off.
|
331
|
+
Specify ssl_certificate_path and ssl_certificate_password if you need
|
332
|
+
certificate verification
|
333
|
+
|
334
|
+
[id="plugins-{type}s-{plugin}-ssl_certificate_password"]
|
335
|
+
===== `ssl_certificate_password`
|
336
|
+
|
337
|
+
* Value type is <<string,string>>
|
338
|
+
* There is no default value for this setting.
|
339
|
+
|
340
|
+
Password for the encrypted PKCS12 (.p12) certificate file specified in ssl_certificate_path
|
341
|
+
|
342
|
+
[id="plugins-{type}s-{plugin}-ssl_certificate_path"]
|
343
|
+
===== `ssl_certificate_path`
|
344
|
+
|
345
|
+
* Value type is <<path,path>>
|
346
|
+
* There is no default value for this setting.
|
347
|
+
|
348
|
+
Path to an SSL certificate in PKCS12 (.p12) format used for verifying the remote host
|
349
|
+
|
350
|
+
[id="plugins-{type}s-{plugin}-ssl_version"]
|
351
|
+
===== `ssl_version`
|
352
|
+
|
353
|
+
* Value type is <<string,string>>
|
354
|
+
* Default value is `"TLSv1.2"`
|
355
|
+
|
356
|
+
Version of the SSL protocol to use.
|
357
|
+
|
358
|
+
[id="plugins-{type}s-{plugin}-subscription_retry_interval_seconds"]
|
359
|
+
===== `subscription_retry_interval_seconds`
|
360
|
+
|
361
|
+
* This is a required setting.
|
362
|
+
* Value type is <<number,number>>
|
363
|
+
* Default value is `5`
|
364
|
+
|
365
|
+
Amount of time in seconds to wait after a failed subscription request
|
366
|
+
before retrying. Subscribes can fail if the server goes away and then comes back.
|
367
|
+
|
368
|
+
[id="plugins-{type}s-{plugin}-threads"]
|
369
|
+
===== `threads`
|
370
|
+
|
371
|
+
* Value type is <<number,number>>
|
372
|
+
* Default value is `1`
|
373
|
+
|
374
|
+
[id="plugins-{type}s-{plugin}-user"]
|
375
|
+
===== `user`
|
376
|
+
|
377
|
+
* Value type is <<string,string>>
|
378
|
+
* Default value is `"guest"`
|
379
|
+
|
380
|
+
RabbitMQ username
|
381
|
+
|
382
|
+
[id="plugins-{type}s-{plugin}-vhost"]
|
383
|
+
===== `vhost`
|
384
|
+
|
385
|
+
* Value type is <<string,string>>
|
386
|
+
* Default value is `"/"`
|
387
|
+
|
388
|
+
The vhost (virtual host) to use. If you don't know what this
|
389
|
+
is, leave the default. With the exception of the default
|
390
|
+
vhost ("/"), names of vhosts should not begin with a forward
|
391
|
+
slash.
|
392
|
+
|
393
|
+
|
394
|
+
|
395
|
+
[id="plugins-{type}s-{plugin}-common-options"]
|
396
|
+
include::{include_path}/{type}.asciidoc[]
|
397
|
+
|
398
|
+
:default_codec!:
|