-
In Graylog 3.0 using a rule that contains the clone_message() function creates an endless loop like described in #4722.
#5284 is related but I believe that this is a bug in the code not in the docu…
-
## Expected Behavior
Changing the referenced grok expression should alter the result of my pipeline.
Even replacing `set_field("original_message", message_field);` with `set_field("event.origi…
-
### Problem description
I have a use case, where I need to remove a sensitive field from a log message, while still maintaining the content of the original message (this is because there is certain…
-
##### SUMMARY
The "service" module somehow utterly fails to handle the "arguments" parameter on OpenBSD targets, never detecting any change, and so never doing anything.
##### ISSUE TYPE
…
-
Fresh install in LXD container can't get it working using Opensearch, works with Elasticsearch 7.10.2.
## Expected Behavior
Work using Opensearch since Elasticsearch 7 will no longer rec…
-
After successful upgrade to 4.3.4 Graylog stopped parsing GeoIP data and ASN data.
It was working just fine on 4.3.3.
Confirmed on 2 different Graylog servers.
GeoIP before:
```
vpn_ext_i…
ghost updated
2 years ago
-
The pipeline rules parser is confused by appending the suffix `_converted` to a field name.
## Expected Behavior
I can use all alphanumeric characters for field names, without any problems. …
-
## Expected Behavior
Graylog is reporting indexer failures with an index and a letter id, but doesn't store the failed message anywhere. This makes it hard to debug and fix those failures.
## Curr…
-
### Discussed in https://github.com/fluent/fluent-bit/discussions/5092
Originally posted by **nitrogene** March 16, 2022
Hello,
I have installed td-agent-bit on wsl2/ubuntu, and have troubl…
-
## Current Behavior
In the Graylog log the following Warning is shown up, i cant find any coherences between tasks in the webinterface and the error message.
2018-01-04T10:50:13.545+01:0…