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]Anomaly score threshold slide bar values are overlaid on Rule Creation page when creating a new Machine Learning rule type #173669

Closed
vgomez-el opened this issue Dec 19, 2023 · 5 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA 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. v8.14.0

Comments

@vgomez-el
Copy link

Describe the bug:

Anomaly score threshold slide bar values are overlapped on ML rule type creation page

Kibana/Elasticsearch Stack version:

8.12 BC 2

Server OS version:

Cloud instance

Browser and Browser OS versions:

Google Chrome Versión 120.0.6099.109 (Official Build) (arm64)

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

Cloud deployment

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

Detection Rules creation

Steps to reproduce:

  1. Go to Rules Management Page
  2. Go to Create a new rule Page
  3. Select Machine learning rule type
  4. Check "Anomaly score threshold" slider values

Current behavior:

All the slide bar values are overlaid on left. Check attached screenshot for more details

Expected behavior:

Values should be displayed properly

Screenshots (if relevant):
image

@vgomez-el vgomez-el added bug Fixes for quality problems that affect the customer experience triage_needed 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. Team:Detection Engine Security Solution Detection Engine Area labels Dec 19, 2023
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@vgomez-el vgomez-el assigned yctercero and vgomez-el and unassigned vgomez-el Dec 20, 2023
@yctercero yctercero removed their assignment Jan 2, 2024
@vitaliidm
Copy link
Contributor

@vgomez-el

It appears, this issue is not happening again.

I check 8.14 locally main branch and 8.13.2 on cloud

Screenshot 2024-04-12 at 17 19 34

Likely was fixed in elastic/eui#7442

@yctercero
Copy link
Contributor

Thanks @vitaliidm - added fixed label to be QA checked.

cc @vgomez-el

@vgomez-el vgomez-el added the QA:Validated Issue has been validated by QA label Apr 16, 2024
@vgomez-el
Copy link
Author

Indeed, it has been fixed in 8.13:
image
Thanks @vitaliidm and @yctercero for taking a look at it!

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 fixed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA 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. v8.14.0
Projects
None yet
Development

No branches or pull requests

4 participants