-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Azure Logs] Replace foreach+set combo with a script processor #34478
[Azure Logs] Replace foreach+set combo with a script processor #34478
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
@andrewkroh, the test file test-non-interactive-user-signin.log contains the key However, the "expected" file test-non-interactive-user-signin.log-expected.json content looks correct. I guess the issue is not evident because the document uses "dot notation" for the fields. WDYT? The integrations repo stores the expected files as a plain JSON document, so this behavior is more visible. |
The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True}
b9fe22e
to
615edbe
Compare
* Replace foreach+set combo with a script processor The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True} * Update changelog (cherry picked from commit a0b2db2)
* Replace foreach+set combo with a script processor The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True} * Update changelog (cherry picked from commit a0b2db2)
… (#34503) * Replace foreach+set combo with a script processor The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True} * Update changelog (cherry picked from commit a0b2db2) Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
… script processor (#34502) * [Azure Logs] Replace foreach+set combo with a script processor (#34478) * Replace foreach+set combo with a script processor The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True} * Update changelog (cherry picked from commit a0b2db2) * Remove unrelated CHANGELOG entries --------- Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
* Replace foreach+set combo with a script processor The `set` processor expands the dots contained in the field name into subfield. Sometimes attributes contained in `authentication_processing_details` have dots, for example: # source {"key": "a.b.c", "value": true} In such cases, the `set` processor would turn it into: # this is a side-effect { "a": { "b": { "c": true } } } Instead of: # this is the expected result {"a.b.c": True} * Update changelog
What does this PR do?
Replace the
foreach
+set
processors combo with a singlescript
processor in the ingest pipeline for Azure AD sign-in logs.Why is it important?
The
set
processor expands the dots contained in the field name into subfields.Sometimes attributes contained in
authentication_processing_details
have dots, for example:In such cases, the
set
processor would turn it into:Instead of:
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues