zscaler_zia: Remove department field and fix parsing errors in web logs - #10874
Merged
Conversation
kcreddy
marked this pull request as ready for review
August 26, 2024 11:20
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
chrisberkhout
self-requested a review
August 26, 2024 14:08
chrisberkhout
requested changes
Aug 26, 2024
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
alerts |
4255.32 | 3571.43 | -683.89 (-16.07%) | 💔 |
endpoint_dlp |
2475.25 | 2008.03 | -467.22 (-18.88%) | 💔 |
tunnel |
4566.21 | 3773.58 | -792.63 (-17.36%) | 💔 |
To see the full report comment with /test benchmark fullreport
This reverts commit 2b88d61.
|
💚 Build Succeeded
History
cc @kcreddy |
chrisberkhout
approved these changes
Aug 27, 2024
|
Package zscaler_zia - 3.2.3 containing this change is available at https://epr.elastic.co/search?package=zscaler_zia |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
…gs (elastic#10874) Remove `department` field and fix parsing errors in web logs. The `department` value is already being ingested from `dept` field. This PR removes the hex-encoded `department` field in favour of `dept` due to noticed improper hex-encoding in fields prefixed with `e` [here](elastic#10855 (comment)). Remove `urldecode` processor on parsing urls causing parsing errors. The `b64url` field is already being decoded by `script` processor. Also adds `on_failure` clause on `urldecode` processors to continue pipeline execution to prevent parsing errors on hex-encoded values to stop running rest of the pipeline.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
…gs (elastic#10874) Remove `department` field and fix parsing errors in web logs. The `department` value is already being ingested from `dept` field. This PR removes the hex-encoded `department` field in favour of `dept` due to noticed improper hex-encoding in fields prefixed with `e` [here](elastic#10855 (comment)). Remove `urldecode` processor on parsing urls causing parsing errors. The `b64url` field is already being decoded by `script` processor. Also adds `on_failure` clause on `urldecode` processors to continue pipeline execution to prevent parsing errors on hex-encoded values to stop running rest of the pipeline.
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.




Proposed commit message
Remove
departmentfield and fix parsing errors in web logs.The
departmentvalue is already being ingested fromdeptfield. This PR removes thehex-encoded
departmentfield in favour ofdeptdue to noticed improper hex-encoding infields prefixed with
ehere.Remove
urldecodeprocessor on parsing urls causing parsing errors. Theb64urlfield is already being decoded by
scriptprocessor.Also adds
on_failureclause onurldecodeprocessors to continue pipeline executionto prevent parsing errors on hex-encoded values to stop running rest of the pipeline.
Checklist
changelog.ymlfile.How to test this PR locally
Ran pipeline tests removing
departmentfield inweblogs. Since there is already adeptfield, the tests are updated with values fromdept.Added new test events with failing
b64urlvalues and verifying the new change doesn't lead to parsing error, and populatesurlECS field.Run pipeline tests:
eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate -v --data-streams=web