Rob Bavey

Results 62 issues of Rob Bavey

This project is intended to provide users with the best experience for using Logstash in a Kubernetes environment. In particular we should document and provide examples including any pain points,...

enhancement
meta
status:work-in-progress
k8s

This meta issue is to track issues with native Java plugins, to determine what we need to ensure that they have parity with traditional ruby/mixed ruby and java plugins. Currently,...

bug
meta
status:confirmed

This meta issue will capture the requirements to enable us to deliver a native M1 version of logstash and publish at the elastic.co download page along with the other released...

enhancement
meta
status:work-in-progress
m1

A standard filter plugin allows implementers to override a `close` method, to release any resources that may have been allocated while the plugin was running - eg releasing a scheduler...

bug
status:needs-triage

**Description of the problem including expected versus actual behavior**: When using json logging, certain events are logged with two `message` entries: ``` { "level" : "WARN", "loggerName" : "logstash.codecs.jsonlines", "timeMillis"...

bug
status:needs-triage
Team:Logstash

When logstash is starting up a pipeline, accessing the monitoring API stats endpoints can yield results, such as: Partial Result ``` { "host" : "computer", "version" : "8.3.0", "http_address" :...

bug
int-shortlist
status:confirmed

[Placeholder tracking issue for now] Currently, logstash telemetry data is derived from stack monitoring data and sent to the telemetry cluster via a Kibana process. This has multiple drawbacks: -...

enhancement
status:needs-triage

Intermittently the `install and run java plugin` test has been hanging, causes the integration test jobs to time out, or need to be manually killed - https://logstash-ci.elastic.co/job/elastic+logstash+pull-request+multijob-integration-pq-1/5583/console ``` 10:13:37 Install...

test failure

Test Failures - [ ] [logstash-filter-grok](https://github.com/logstash-plugins/logstash-filter-grok): https://github.com/logstash-plugins/logstash-filter-grok/issues/178 - [ ] [logstash-filter-fingerprint](https://github.com/logstash-plugins/logstash-filter-fingerprint): https://github.com/logstash-plugins/logstash-filter-fingerprint/issues/68 - [ ] [logstash-filter-useragent](https://github.com/logstash-plugins/logstash-filter-useragent): https://github.com/logstash-plugins/logstash-filter-useragent/issues/81 - [ ] [logstash-input-syslog](https://github.com/logstash-plugins/logstash-input-syslog): https://github.com/logstash-plugins/logstash-input-syslog/issues/70 - [ ] [logstash-input-snmp](https://github.com/logstash-plugins/logstash-input-snmp): https://github.com/logstash-plugins/logstash-input-snmp/issues/107 - [ ]...

A number of syslog specs are failing on Logstash 8.x: ``` logstash_1_4ac9a179a5f3 | 1) LogStash::Filters::Grok ietf 5424 syslog line 1 2009-06-30T18:30:00+02:00 paxton.local grokdebug - - [id1 foo="bar"] No process ID....

test failure