Rob Bavey

https://app.travis-ci.com/github/logstash-plugins/logstash-codec-netflow/jobs/572876184 ``` logstash_1_d30bd60076cc | LogStash::Codecs::Netflow logstash_1_d30bd60076cc | Netflow 9 invalid 01 logstash_1_d30bd60076cc | should not raise_error logstash_1_d30bd60076cc | IPFIX VMware virtual distributed switch logstash_1_d30bd60076cc | should serialize to json (FAILED...

[Meta] Stack monitoring documentation issues

2

This meta issue will collect a list of known issues with the documentation of stack monitoring of Logstash - [x] #14661 - [ ] #15122 - Also our overview page...

We should add notes to the effect that when running Logstash on a Windows box, users should consider setting up antivirus exclusions for certain folders, otherwise Logstash stability may be...

Currently, we maintain two separate white-listed settings of per-pipeline settings: * A list used when reading [pipelines.yml](https://github.com/elastic/logstash/blob/c8812eeb9151173715f233f97905c2daf5580cfe/logstash-core/lib/logstash/settings.rb#L44-L78) * A list used when retrieving the pipeline from [Elasticsearch](https://github.com/elastic/logstash/blob/c8812eeb9151173715f233f97905c2daf5580cfe/x-pack/lib/config_management/elasticsearch_source.rb#L26-L35) Historically, we have...

Add support for `setMaxInboundMessageBodySize`

1

This commit adds an additional parameter to #connect to support setting the maximum size of inbound messages.

Disable allow_superuser by default

2

In https://github.com/elastic/logstash/pull/14046 and https://github.com/elastic/logstash/pull/14089, we introduced new functionality to guard against running Logstash as root with the introduction of a new setting `allow_superuser`. The initial implementation set this to `true`...

Set `pipeline.buffer.type` to `heap` by default

3

In #16054, we introduced a new setting to allow users to set the allocation of memory for certain input plugins to use either direct or heap memory. We should consider...

For `9.0.0`, we should clean up `jvm.options`, and remove any options that are no longer applicable.

For `9.0.0`, we should remove any plugin settings that are currently marked as `obsolete`

These modules have been long deprecated from Logstash, having been superseded by agent integrations, and should be removed.