Update README indicating logstash v6 support. Add some additional configuration options to the README. Upgrade Rubocop.
This commit is contained in:
parent
aba4e08bf5
commit
309768c893
|
@ -56,6 +56,8 @@ For development:
|
||||||
| retry_initial_interval | Number | Number of seconds before the initial retry in the event of a failure. On each failure it will be doubled until it reaches retry_max_interval | No | 2 |
|
| retry_initial_interval | Number | Number of seconds before the initial retry in the event of a failure. On each failure it will be doubled until it reaches retry_max_interval | No | 2 |
|
||||||
| retry_max_interval | Number | Maximum number of seconds between each retry | No | 128 |
|
| retry_max_interval | Number | Maximum number of seconds between each retry | No | 128 |
|
||||||
| retry_sql_states | Array of strings | An array of custom SQL state codes you wish to retry until `max_flush_exceptions`. Useful if you're using a JDBC driver which returns retry-able, but non-standard SQL state codes in it's exceptions. | No | [] |
|
| retry_sql_states | Array of strings | An array of custom SQL state codes you wish to retry until `max_flush_exceptions`. Useful if you're using a JDBC driver which returns retry-able, but non-standard SQL state codes in it's exceptions. | No | [] |
|
||||||
|
| event_as_json_keyword | String | The magic key word that the plugin looks for to convert the entire event into a JSON object. As Logstash does not support this out of the box with it's `sprintf` implementation, you can use whatever this field is set to in the statement parameters | No | @event |
|
||||||
|
| enable_event_as_json_keyword | Boolean | Enables the magic keyword set in the configuration option `event_as_json_keyword`. Without this enabled the plugin will not convert the `event_as_json_keyword` into JSON encoding of the entire event. | No | False |
|
||||||
|
|
||||||
## Example configurations
|
## Example configurations
|
||||||
Example logstash configurations, can now be found in the examples directory. Where possible we try to link every configuration with a tested jar.
|
Example logstash configurations, can now be found in the examples directory. Where possible we try to link every configuration with a tested jar.
|
||||||
|
|
|
@ -34,5 +34,5 @@ Gem::Specification.new do |s|
|
||||||
|
|
||||||
s.add_development_dependency "logstash-devutils", "~> 1.3", ">= 1.3.1"
|
s.add_development_dependency "logstash-devutils", "~> 1.3", ">= 1.3.1"
|
||||||
|
|
||||||
s.add_development_dependency 'rubocop', '0.41.2'
|
s.add_development_dependency 'rubocop', '~> 0.51.0'
|
||||||
end
|
end
|
||||||
|
|
Loading…
Reference in New Issue
Block a user