[Packetbeat] Fix data stream name for network flows under Agent #28408
Conversation
This file contains 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
This fixes and issue with network flows being written to the wrong
index when using the Network Packet Capture integration in Fleet.
The error was:
{"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"}
The cause is that flows were setting `index` rather than `raw_index`. With
`index` Beats adds the date suffix, but since this is a data stream we
want `raw_index` where the value passes through as-is.
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
added
needs_team
mergify
bot
added
the
backport-skip
andrewkroh
added
backport-v7.15.0
|
There weren't any existing integrations test that I could find for this. |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
Edit: no, similar fix, different issue. |
efd6
approved these changes
Oct 13, 2021
mergify bot
pushed a commit
that referenced
this pull request
Oct 15, 2021
* Fix data stream name for network flows under Agent
This fixes and issue with network flows being written to the wrong
index when using the Network Packet Capture integration in Fleet.
The error was:
{"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"}
The cause is that flows were setting `index` rather than `raw_index`. With
`index` Beats adds the date suffix, but since this is a data stream we
want `raw_index` where the value passes through as-is.
(cherry picked from commit 5c92897)
mergify bot
pushed a commit
that referenced
this pull request
Oct 15, 2021
* Fix data stream name for network flows under Agent
This fixes and issue with network flows being written to the wrong
index when using the Network Packet Capture integration in Fleet.
The error was:
{"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"}
The cause is that flows were setting `index` rather than `raw_index`. With
`index` Beats adds the date suffix, but since this is a data stream we
want `raw_index` where the value passes through as-is.
(cherry picked from commit 5c92897)
andrewkroh
added a commit
that referenced
this pull request
Oct 18, 2021
…) (#28469) * Fix data stream name for network flows under Agent This fixes and issue with network flows being written to the wrong index when using the Network Packet Capture integration in Fleet. The error was: {"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"} The cause is that flows were setting `index` rather than `raw_index`. With `index` Beats adds the date suffix, but since this is a data stream we want `raw_index` where the value passes through as-is. (cherry picked from commit 5c92897) Co-authored-by: Andrew Kroh <[email protected]>
andrewkroh
added a commit
that referenced
this pull request
Oct 18, 2021
…) (#28468) * Fix data stream name for network flows under Agent This fixes and issue with network flows being written to the wrong index when using the Network Packet Capture integration in Fleet. The error was: {"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"} The cause is that flows were setting `index` rather than `raw_index`. With `index` Beats adds the date suffix, but since this is a data stream we want `raw_index` where the value passes through as-is. (cherry picked from commit 5c92897) Co-authored-by: Andrew Kroh <[email protected]>
Icedroid
pushed a commit
to Icedroid/beats
that referenced
this pull request
Nov 1, 2021
…tic#28408) * Fix data stream name for network flows under Agent This fixes and issue with network flows being written to the wrong index when using the Network Packet Capture integration in Fleet. The error was: {"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"} The cause is that flows were setting `index` rather than `raw_index`. With `index` Beats adds the date suffix, but since this is a data stream we want `raw_index` where the value passes through as-is.
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.
What does this PR do?
This fixes and issue with network flows being written to the wrong
index (it should not include any date) when using the Network Packet Capture integration in Fleet.
The error was:
{"type:"security_exception", "reason":"action [indices:admin/auto_create] is unauthorized for API key id [xxx] of user [elastic/fleet-server] on indices [logs-network_traffic.flow-default-2021.10.13] …"}The cause is that flows were setting
indexrather thanraw_index. WithindexBeats adds the date suffix, but since this is a data stream wewant
raw_indexwhere the value passes through as-is.Why is it important?
Fleet could not ingest network flows from Packetbeat.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Links
Also reported in https://discuss.elastic.co/t/is-network-traffic-fleet-integration-the-new-packetbeat-missing-netfow/285636.