Push events to a GemFire region.
GemFire is an object database.
To use this plugin you need to add gemfire.jar to your CLASSPATH. Using format=json requires jackson.jar too; use of continuous queries requires antlr.jar.
Note: this plugin has only been tested with GemFire 7.0.
input {
gemfire {
add_field => ... # hash (optional), default: {}
cache_name => ... # string (optional), default: "logstash"
cache_xml_file => ... # string (optional), default: nil
codec => ... # codec (optional), default: "plain"
interest_regexp => ... # string (optional), default: ".*"
query => ... # string (optional), default: nil
region_name => ... # string (optional), default: "Logstash"
serialization => ... # string (optional), default: nil
tags => ... # array (optional)
threads => ... # number (optional), default: 1
type => ... # string (optional)
}
}
Add a field to an event
Your client cache name
The path to a GemFire client cache XML file.
Example:
<client-cache>
<pool name="client-pool" subscription-enabled="true" subscription-redundancy="1">
<locator host="localhost" port="31331"/>
</pool>
<region name="Logstash">
<region-attributes refid="CACHING_PROXY" pool-name="client-pool" >
</region-attributes>
</region>
</client-cache>
The character encoding used in this input. Examples include “UTF-8” and “cp1252”
This setting is useful if your log files are in Latin-1 (aka cp1252) or in another character set other than UTF-8.
This only affects “plain” format logs since json is UTF-8 already.
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.
The format of input data (plain, json, json_event)
A regexp to use when registering interest for cache events. Ignored if a :query is specified.
If format is “json”, an event sprintf string to build what the display @message should be given (defaults to the raw JSON). sprintf format strings look like %{fieldname}
If format is “json_event”, ALL fields except for @type are expected to be present. Not receiving all fields will cause unexpected results.
A query to run as a GemFire “continuous query”; if specified it takes precedence over :interest_regexp which will be ignore.
Important: use of continuous queries requires subscriptions to be enabled on the client pool.
The region name
How the message is serialized in the cache. Can be one of “json” or “plain”; default is plain
Add any number of arbitrary tags to your event.
This can help with processing later.
Set this to the number of threads you want this input to spawn. This is the same as declaring the input multiple times
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 the web interface.
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.