-
Notifications
You must be signed in to change notification settings - Fork 474
[System] Fix indentation of tags inside syslog datastream #8345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🌐 Coverage report
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
"name": "thermald" | ||
}, | ||
"system": { | ||
"syslog": {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just trying to understand the data that we receive in the system.syslog
field. The test logs and the sample events doesn't log any data into this field and the ingest GROK pattern too doesn't process data in the system.syslog
field. Can we consider removing the field definition in fields.yml
if we are not going to log data in system.syslog field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muthu-mps Maybe the field is there to let users have their custom fields into this group using the @custom
pipeline.
But if its not needed, can you create another issue/PR? I only added some fields because the system tests were failing otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This empty object is result of deleting all of the keys from within the syslog
map. We should be removing it via the ingest pipeline if it is entirely empty.
It would probably be simpler to write the output of the grok into _temp
rather than system.syslog
if we will always be renaming everything under system.syslog.*
such that it becomes empty. Then we can unconditionally remove _temp
at the end.
Package system - 1.47.1 containing this change is available at https://epr.elastic.co/search?package=system |
2 similar comments
Package system - 1.47.1 containing this change is available at https://epr.elastic.co/search?package=system |
Package system - 1.47.1 containing this change is available at https://epr.elastic.co/search?package=system |
Proposed commit message
system.syslog
input configuration.system.syslog
datastreamChecklist
changelog.yml
file.Author's Checklist
How to test this PR locally
$ elastic-package stack down && elastic-package build && elastic-package stack up --version=8.10.3 -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test system --generate --data-streams syslog -v
Related issues
Screenshots