The Get snapshot API does not include the .fleet-actions-results system data stream in the fleet feature state information. This discrepancy is observed despite the data stream being present in the snapshot's data streams.
Steps to Reproduce
Create a cluster with version 8.14.3 in ESS.
Deploy an Elastic Agent with the Osquery Manager integration.
Run a new live Osquery.
Observe that the .fleet-actions-results data stream is created with the respective backing indices.
Take a snapshot.
Run the Get snapshot API on the same snapshot.
Observe that the .fleet-actions-results system data stream is missing in the fleet feature state reported by the Get snapshot API.
Expected Behavior
The response from the Get snapshot API should include the .fleet-actions-results data stream under the fleet feature state, as shown in the example below:
Description
Elasticsearch Version
8.14.3
Problem Description
The
Get snapshot
API does not include the.fleet-actions-results
system data stream in the fleet feature state information. This discrepancy is observed despite the data stream being present in the snapshot's data streams.Steps to Reproduce
.fleet-actions-results
data stream is created with the respective backing indices.Get snapshot
API on the same snapshot..fleet-actions-results
system data stream is missing in the fleet feature state reported by theGet snapshot
API.Expected Behavior
The response from the
Get snapshot
API should include the.fleet-actions-results
data stream under thefleet
feature state, as shown in the example below:JSON response (actual)