-
Notifications
You must be signed in to change notification settings - Fork 392
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
windows: harmonise powershell details regexp patterns #7192
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.
Can we add similar pipeline tests here too?
packages/windows/data_stream/forwarded/elasticsearch/ingest_pipeline/powershell_operational.yml
Outdated
Show resolved
Hide resolved
The details regexp pattern for the powershell data stream was improved to reduce backtracking costs that caused regexp costs to exceed the set runtime limits. The same pattern on other data streams was not updated. This change brings them up to date with the change.
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.
LGTM.
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.
LGTM
Package windows - 1.28.1 containing this change is available at https://epr.elastic.co/search?package=windows |
The details regexp pattern for the powershell data stream was improved to reduce backtracking costs that caused regexp costs to exceed the set runtime limits. The same pattern on other data streams was not updated. This change brings them up to date with the change.
What does this PR do?
The details regexp pattern for the powershell data stream was improved in #6154 to reduce backtracking costs that caused regexp costs to exceed the set runtime limits. The same pattern on other data streams was not updated. This change brings them up to date with the change.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots