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

[Security Solution] Detections fail when an index is missing a primary shard #101990

Open
Tracked by #165878
BenB196 opened this issue Jun 11, 2021 · 2 comments
Open
Tracked by #165878
Labels
bug Fixes for quality problems that affect the customer experience enhancement New value added to drive a business result Feature:Detection Alerts Security Solution Detection Alerts Feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@BenB196
Copy link

BenB196 commented Jun 11, 2021

Describe the bug:

If there is an index that is used in a detection rule, and that index is missing a primary shard (cluster in red state), the detection rules that use that index will fail with the error:

Bulk Indexing of signals failed: index: "<index_with_primary_shard_missing>" reason: "[<node_with_missing_shard>][127.0.0.1:9300][indices:data/read/search[phase/query]]" type: "no_shard_available_action_exception" name: "<detection_rule_name>" id: "ac117e42-a91f-11eb-a252-7f35a8822039" rule id: "5e552599-ddec-4e14-bad1-28aa42404388" signals index: ".siem-signals-security"

This results in the detection rule(s) not running, and therefore not detecting things.

Kibana/Elasticsearch Stack version:

Elasticsearch: 7.13.1
Kibana: 7.13.1

Server OS version:

OS: Docker/ECK

Browser and Browser OS versions:

N/A

Elastic Endpoint version:

N/A

Original install method (e.g. download page, yum, from source, etc.):

ECK

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

Detections

Steps to reproduce:

  1. Create a detection rule that uses an index pattern. ex: filebeat-*
  2. Create two indices, filebeat-1, filebeat-2
  3. Start detection rule
  4. Cause a primary shard to fail on filebeat-1
  5. Detection rule will fail

Current behavior:

Detection rule fails when a primary shard is missing. This results in no detections occurring at all.

Expected behavior:

Detection rule should still work, but should instead show as warning. Detections should still trigger from the available indices.

Screenshots (if relevant):

N/A

Errors in browser console (if relevant):

N/A

Provide logs and/or server output (if relevant):

N/A

Any additional context (logs, chat logs, magical formulas, etc.):

I know that a red cluster state is bad, but sometimes it happens, and I would expect a security solution to best effort maintain monitoring of the environment while the red state is resolved.

@BenB196 BenB196 added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Jun 11, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@peluja1012 peluja1012 added triage_needed Team:Detections and Resp Security Detection Response Team labels Aug 11, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@MadameSheema MadameSheema added Feature:Detection Alerts Security Solution Detection Alerts Feature Team:Detection Alerts Security Detection Alerts Area Team enhancement New value added to drive a business result and removed triage_needed labels Sep 29, 2021
@marshallmain marshallmain added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Mar 29, 2022
@marshallmain marshallmain added v8.7.0 and removed v8.6.0 labels Dec 1, 2022
@yctercero yctercero added Team:Detection Engine Security Solution Detection Engine Area and removed Team:Detection Alerts Security Detection Alerts Area Team labels May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience enhancement New value added to drive a business result Feature:Detection Alerts Security Solution Detection Alerts Feature impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

7 participants