-
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
netflow: Use internal and external for locality fields #24295
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Changes netflow input to use internal and external for locality fields: - source.locality - destination.locality - flow.locality Previously it was using public and private. Fixes elastic#24272 (cherry picked from commit 0c6acc9)
Changes netflow input to use internal and external for locality fields: - source.locality - destination.locality - flow.locality Previously it was using public and private. Fixes elastic#24272 (cherry picked from commit 0c6acc9)
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 5375 |
Skipped | 738 |
Total | 6113 |
elastic#24461) Changes netflow input to use internal and external for locality fields: - source.locality - destination.locality - flow.locality Previously it was using public and private. Fixes elastic#24272 (cherry picked from commit a1a8d7a)
What does this PR do?
Changes netflow input to use
internal
andexternal
for locality fields:Previously it was using
public
andprivate
.Why is it important?
There was a mismatch between the output values and the values expected by the ingest pipeline used by the Netflow module. Also the new values make more sense from a locality perspective.
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Closes #24272