This output lets you store logs in elasticsearch. It's similar to the 'elasticsearch' output but improves performance by using an AMQP server, such as rabbitmq, to send data to elasticsearch.
Upon startup, this output will automatically contact an elasticsearch cluster and configure it to read from the queue to which we write.
You can learn more about elasticseasrch at http://elasticsearch.org More about the elasticsearch rabbitmq river plugin: https://github.com/elasticsearch/elasticsearch-river-rabbitmq/blob/master/README.md
output {
elasticsearch_river {
amqp_host => ... # string (required)
amqp_port => ... # number (optional), default: 5672
debug => ... # boolean (optional)
durable => ... # boolean (optional), default: true
es_bulk_size => ... # number (optional), default: 1000
es_bulk_timeout_ms => ... # number (optional), default: 100
es_host => ... # string (required)
es_port => ... # number (optional), default: 9200
exchange => ... # string (optional), default: "elasticsearch"
exchange_type => ... # ["fanout", "direct", "topic"] (optional), default: "direct"
index => ... # string (optional), default: "logstash-%{+YYYY.MM.dd}"
index_type => ... # string (optional), default: "%{@type}"
key => ... # string (optional), default: "elasticsearch"
name => ... # string (optional), default: "elasticsearch"
password => ... # string (optional), default: "guest"
persistent => ... # boolean (optional), default: true
tags => ... # array (optional), default: []
type => ... # string (optional), default: ""
user => ... # string (optional), default: "guest"
vhost => ... # string (optional), default: "/"
}
}
Hostname of AMQP server
Port of AMQP server
AMQP durability setting. Also used for ElasticSearch setting
ElasticSearch river configuration: bulk fetch size
ElasticSearch river configuration: bulk timeout in milliseconds
The name/address of an ElasticSearch host to use for river creation
ElasticSearch API port
AMQP exchange name
The exchange type (fanout, topic, direct)
The index to write events to. This can be dynamic using the %{foo} syntax. The default value will partition your indeces by day so you can more easily delete old data or only search specific date ranges.
The index type to write events to. Generally you should try to write only similar events to the same 'type'. String expansion '%{foo}' works here.
AMQP routing key
AMQP queue name
AMQP password
AMQP persistence setting
Only handle events with all of these tags. Note that if you specify a type, the event must also match that type. Optional.
The type to act on. If a type is given, then this output will only act on messages with the same type. See any input plugin's "type" attribute for more. Optional.
AMQP user
AMQP vhost