Add action responses data stream#9661
Add action responses data stream#9661aleksmaus merged 2 commits intoelastic:mainfrom aleksmaus:feature/action_responses_datastream
Conversation
|
This PR currently fails CI because 8.15 build specified in the manifest is not available at the moment. |
|
/test |
|
💚 Build Succeeded
History
|
…#183892) **Prerequisite**: elastic/elasticsearch#108849 **Follow-up**: elastic/integrations#9661 This PR introduces a new index `logs-osquery_manager.action.responses-default` for action responses. This index will be added in Osquery Manager integration version `1.12` and 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.
There was a problem hiding this comment.
I tested the latest changes in Kibana, which expect the new index to exist. If it doesn't, it falls back to the current one. I confirmed that these changes work across all Osquery functionalities in Kibana:
- Live query / Pack live query
- Query history
- Pack periodic runs
- Automated response actions
In all these scenarios, I observed the logs-osquery_manager.action.responses-default index being properly populated and consumed by Kibana.
|
Package osquery_manager - 1.12.0 containing this change is available at https://epr.elastic.co/search?package=osquery_manager |
|
Heya, the issue that's referenced in the description, https://github.com/elastic/security-team/issues/8893 , does not seem to be accessible. |




Proposed commit message
Add action responses data stream:
logs-osquery_manager.action.responses-defaultThis allows osquerybeat to post the actions responses directly to elasticsearch and fix the issues with the current the transform job based approach, where the actions results could be lost at scale, and presently there is no better solution to address this at the elasticsearch stack.
For more details check this ticket:
https://github.com/elastic/security-team/issues/8893
Since the results are now posted into the proper
logs-osquery_manager.action.responses-defaultdatastream, Kibana would need to be adjusted to use it instead of the currently used index.logs-osquery_manager.action.responses-defaultThere will be the osquerybeat PR with corresponding changes, related to this.
The package manifest updated constraint to 8.15 version of the stack.
Checklist
changelog.ymlfile.How to test this PR locally
Full regression testing.
Related issues
Screenshots
The new
logs-osquery_manager.action.responses-defaultdocument example: