-
Notifications
You must be signed in to change notification settings - Fork 474
[system] Fix condition in handlebar file of security data stream #14674
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
[system] Fix condition in handlebar file of security data stream #14674
Conversation
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
syslog |
500000 | 333333.33 | -166666.67 (-33.33%) | 💔 |
To see the full report comment with /test benchmark fullreport
For the future, Policy testing can be added to catch errors when updating Handlebars: https://github.com/elastic/elastic-package/blob/main/docs/howto/policy_testing.md For context, a similar error happened to me when editing the handlebars file in the Auditd Manager integration, and then we learned that policy tests spin a Kibana Snapshot to attempt to save an integration policy, which will catch errors with the handlebars. Here is how they are configured in AuditdManager |
|
💚 Build Succeeded
History
|
Package system - 2.5.1 containing this change is available at https://epr.elastic.co/package/system/2.5.1/ |
Proposed commit message
Checklist
changelog.yml
file.How to test this PR locally