system.auth - sync pipeline with Fleet integration#32360
Merged
andrewkroh merged 5 commits intoelastic:mainfrom Jul 20, 2022
Merged
system.auth - sync pipeline with Fleet integration#32360andrewkroh merged 5 commits intoelastic:mainfrom
andrewkroh merged 5 commits intoelastic:mainfrom
Conversation
Contributor
Contributor
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Sync the pipeline for the system.auth dataset with the Fleet integration from elastic/integrations#3705. This removes the event.type authentication_failed and authentication_success values which are not allowed as per ECS. You can use event.category: authentication and event.outcome: success/failure to query instead.
9f22768 to
f468b2a
Compare
Contributor
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
belimawr
approved these changes
Jul 20, 2022
mergify bot
pushed a commit
that referenced
this pull request
Jul 20, 2022
Sync the pipeline for the system.auth dataset with the Fleet integration from elastic/integrations#3705. This removes the event.type authentication_failed and authentication_success values which are not allowed as per ECS. You can use event.category: authentication and event.outcome: success/failure to query instead. (cherry picked from commit 475dd7e)
andrewkroh
added a commit
that referenced
this pull request
Jul 26, 2022
…ation (#32422) * system.auth - sync pipeline with Fleet integration (#32360) Sync the pipeline for the system.auth dataset with the Fleet integration from elastic/integrations#3705. This removes the event.type authentication_failed and authentication_success values which are not allowed as per ECS. You can use event.category: authentication and event.outcome: success/failure to query instead. (cherry picked from commit 475dd7e) * Update go-ucfg to v0.8.6 The module tests were failing because the empty tags array was being discarded resulting in the tags value being treated as `nil`. And this was not being accepted as a valid type for the inList function. The cause was elastic/go-ucfg#188. * Fix tests affected by go-ucfg upgrade Backport fix from 0022ea4. Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
4 tasks
Contributor
|
@andrewkroh this PR has broken Filebeat->Logstash->Elasticsearch for
and consider reverting to use |
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
Sync the pipeline for the system.auth dataset with the Fleet integration from elastic/integrations#3705. This removes the event.type authentication_failed and authentication_success values which are not allowed as per ECS. You can use event.category: authentication and event.outcome: success/failure to query instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Sync the pipeline for the system.auth dataset with the Fleet integration
from elastic/integrations#3705.
This removes the event.type authentication_failed and authentication_success
values which are not allowed as per ECS. You can use event.category: authentication
and event.outcome: success/failure to query instead.
Why is it important?
This should make the pipeline more efficient and it aligns the event.type field to ECS.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues