Andres Rodriguez
Andres Rodriguez
**Description of the problem including expected versus actual behavior**: When upgrading Logstash from any release equal or earlier than 7.9.3 (noarch) to any later release, namely 7.10.0 and later, the...
The Logstash systemd unit for Deb/RPMs declares the use of `/etc/default/logstash` as `EnvironmentFile`, but it does not use variables. As such, any chances that the user makes in `/etc/default/logstash` won't...
This issue tracks all the items that need to be handled for the 8.0 release. - [ ] **Support Breaking Changes in Stack Components**: - [ ] Elasticsearch finalizing Types...
When using logstash from deb/rpms or the elastic archive, Logstash systemd unit doesn't create pidfiles, hence, completely ignoring what's set it /etc/default. Version: 7.9 Operating System: Centos 7 / Ubuntu...
## What does this PR do? Updates the docs to correctly display JDK17 as the default JDK version. ## Why is it important/What is the impact to the user? Current...
Java 21 is now available and we would like to make it the default for Logstash. However, we need to investigate whether it is possible provided Jruby supports it. Deprecation...
There is a corner case when that when a comment symbol is present on EOF on a Logstash Pipeline configuration, Logstash errors out. An example of this is when a...
This is my config: ``` input { http { port => 8080 ssl_enabled => true ssl_key => "/etc/logstash/certs/logstash/logstash.pkcs8.key" ssl_certificate => "/etc/logstash/certs/logstash/logstash.crt" ssl_certificate_authorities => ["/etc/logstash/certs/ca/ca.crt"] ssl_client_authentication => required } } ```...
Set's the correct ownership for the Logstash Buildkite pipelines