-
> How would that play with the idea of splitting up the multi tenant filter?
Personally I remain unconvinced that this is even a problem, never mind a problem that's worth trying to d…
-
[Grok documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/grok-processor.html#:~:text=Returns%20on%20the%20first%20expression%20in%20the%20list%20that%20matches.) says the f…
-
This is a feature request pertaining to the capabilities of pipeline rules. The suggestion is to add support for looping over Map results in order to cover important use cases for functions returning …
ghost updated
2 years ago
-
# Integration release checklist
The PostgreSQL Audit Extension (or pgaudit) provides detailed session and/or object audit logging via the standard logging facility provided by PostgreSQL.
More inf…
narph updated
8 months ago
-
I've added
`logger.jsonfilter.name = logstash.filters.json`
`logger.jsonfilter.level = off`
`logger.grokfilter.name = logstash.filters.grok`
`logger.grokfilter.level = off`
to _/etc/logstash/log4…
-
# Integration release checklist
Sysdig is a comprehensive security platform that combines different security approaches to protect cloud infrastructure and cloud native applications.
We would li…
-
The s3 input plugin does not store the position of the file it was busy processing when it detected that it should stop.
From the log file, you can see that the following code was called:
```
@logg…
-
Currently this plugin loads patterns from the `patterns/` directory within `logstash-patterns-core` and also from `$LOGSTASH_HOME/patterns` by default:
```
@@patterns_path ||= Set.new
@@p…
-
OS: CentOS 7.1
Logstash: 2.0.0
Java: OpenJDK 1.8.0_65
Filter:
filter {
if [type] == 'accesslog' {
grok{
match => {'message' => "%{COMBINEDAPACHELOG} - %{NUMBER:responseTime} ms"}
…
-
```
If I could run grep or grok matching patterns and then if it matches I could
send(output) again it to a AMQP queue, I could do a lot of stuffs doing this.
Some thoughts:
- I can do a post proces…