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][Serverless][8.16] Suppression isn't labeled as optional for Threshold rules #197355

Open
nastasha-solomon opened this issue Oct 23, 2024 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@nastasha-solomon
Copy link
Contributor

Describe the bug:

The Suppress alerts field isn't labeled as optional in the rule creation form for Threshold rules.

Kibana/Elasticsearch Stack version: 8.16

Server OS version: N/A

Browser and Browser OS versions: N/A

Elastic Endpoint version: N/A

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

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

Steps to reproduce:

  1. Go to Rules → Detection rules (SIEM) → Create new rule.
  2. Select Threshold.
  3. Scroll down to the Suppress alerts field.

Current behavior:
The Suppress alerts field isn't labeled as optional.

Expected behavior:
The Suppress alerts field should be labeled as optional.

Screenshots (if relevant): See above

Errors in browser console (if relevant): N/A

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

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

@nastasha-solomon nastasha-solomon added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Engine Security Solution Detection Engine Area triage_needed labels Oct 23, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@elasticmachine
Copy link
Contributor

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

@yctercero yctercero added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed triage_needed labels Nov 4, 2024
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 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

3 participants