You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
When multiple concrete indices (and possibly aliases) are configured against a detector the query index is only creating the query for the first index that's selected but not the subsequent indices. Then when you ingest a document into one of the indices that don't have the correct query, a finding is not generated. However, it is created for the index with the correct query in the query index.
How can one reproduce the bug?
Steps to reproduce the behavior:
Create a detector with multiple concrete indices.
Check the query index and only 1 query should be created from that detector.
Try to generate a finding using an index that doesn't have a query
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
OS: 2.17
Version [e.g. 22]
Plugins
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered:
jowg-amazon
changed the title
[BUG]
[BUG] No findings for detector configured against multiple concrete indices
Dec 13, 2024
jowg-amazon
changed the title
[BUG] No findings for detector configured against multiple concrete indices
[BUG] Missing findings for detector configured against multiple concrete indices
Dec 16, 2024
What is the bug?
When multiple concrete indices (and possibly aliases) are configured against a detector the query index is only creating the query for the first index that's selected but not the subsequent indices. Then when you ingest a document into one of the indices that don't have the correct query, a finding is not generated. However, it is created for the index with the correct query in the query index.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: