Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Impossible to create/update detector when one data source index is closed #1103

Open
lsoumille opened this issue Jun 27, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@lsoumille
Copy link

What is the bug?
It's impossible to create or update a detector when one index behind the alias data source is closed

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Edit an existing detector
  2. Pick an alias as data source with a closed index
  3. Save your changes

What is the expected behavior?
We would expect to update to be able to create or update a detector even though all the index behind the data source are not opened. In our case we are closing indexing older than 1 month to keep a good search performance. We keep them for some time in case of an incident.

What is your host/environment?

  • OS: WS2022
  • Version 2.15
  • Plugins

Do you have any screenshots?
image

Do you have any additional context?
I tried to open all the old indexes we have in the cluster and it solved the issue. However the detector is able to detect newly suspicious behaviours

@lsoumille lsoumille added bug Something isn't working untriaged labels Jun 27, 2024
@lsoumille lsoumille changed the title [BUG] [BUG] Impossible to create/update detector when one data source index is closed Jun 27, 2024
@dblock
Copy link
Member

dblock commented Jul 15, 2024

[Catch All Triage - 1, 2, 3]

@dblock dblock removed the untriaged label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants