For other versions, see theVersioned plugin docs.
For plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-output-solr_http
. See Working with plugins for more details.
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.
This output lets you index&store your logs in Solr. If you want to getstarted quickly you should use version 4.4 or above in schemaless mode,which will try and guess your fields automatically. To turn that on,you can use the example included in the Solr archive:
tar zxf solr-4.4.0.tgzcd examplemv solr solr_ #back up the existing sample confcp -r example-schemaless/solr/ . #put the schemaless conf in placejava -jar start.jar #start Solr
You can learn more at the Solr home page
This plugin supports the following configuration options plus the Common Options described later.
Setting | Input type | Required |
---|---|---|
No |
||
No |
||
No |
||
No |
Also see Common Options for a list of options supported by alloutput plugins.
nil
Solr document ID for events. You’d typically have a variable here, like
100
Number of events to queue up before writing to Solr
1
Amount of time since the last flush before a flush is done even ifthe number of buffered events is smaller than flush_size
"http://localhost:8983/solr"
URL used to connect to Solr
The following configuration options are supported by all output plugins:
"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.
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 collectionfor a specific plugin.
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 usefulwhen you have two or more plugins of the same type. For example, if you have 2 solr_http outputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { solr_http { id => "my_plugin_id" }}