[EDR Workflows][Osquery] Use newly added action responses data stream#183892
Merged
szwarckonrad merged 5 commits intoelastic:mainfrom May 24, 2024
Merged
[EDR Workflows][Osquery] Use newly added action responses data stream#183892szwarckonrad merged 5 commits intoelastic:mainfrom
szwarckonrad merged 5 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
patrykkopycinski
approved these changes
May 23, 2024
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.
Prerequisite: elastic/elasticsearch#108849
Follow-up: elastic/integrations#9661
This PR introduces a new index
logs-osquery_manager.action.responses-defaultfor action responses. This index will be added in Osquery Manager integration version1.12and will replace the existing.logs-osquery_manager.action.responses-default, which is currently populated by a transform from.fleet-actions.Since most users will still be using the old integration package, we ensured that the implementation checks the old index first and returns the response from there unless the new index is available. If the new index is available, the response will come from it. This change ensures compatibility with all user scenarios.