[Security Solution][Detections] Signals migration status endpoint contains unrelated system indices #100305
Labels
bug
Fixes for quality problems that affect the customer experience
impact:high
Addressing this issue will have a high level of impact on the quality/strength of our product.
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
v7.14.0
Due to the addition of kibana system datastreams and the behavior addressed in elastic/elasticsearch#72953, the current behavior on master is that the migration status endpoint contains unrelated indices:
Example response
```json { "indices": [ { "index": ".siem-signals-default-000001", "version": 35, "signal_versions": [ { "version": 35, "count": 60 } ], "migrations": [], "is_outdated": false }, { "index": ".ds-ilm-history-5-2021.05.06-000001", "version": 0, "signal_versions": [ { "version": "0", "count": 12 } ], "migrations": [], "is_outdated": true } ] } ```While those indices are unable to be migrated via the API and thus do not pose any data integrity issue, their appearance in the status API is bad UX. Luckily, the above PR should address this behavior.
This issue, then, is meant to note the current behavior and serve as a reminder to verify the above fix and unskip the corresponding integration test from #99915.
The text was updated successfully, but these errors were encountered: