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

[ML] Explain Log Rate Spikes: Brush styles not being applied on first render. #139021

Closed
Tracked by #138117
walterra opened this issue Aug 17, 2022 · 2 comments · Fixed by #141545
Closed
Tracked by #138117

[ML] Explain Log Rate Spikes: Brush styles not being applied on first render. #139021

walterra opened this issue Aug 17, 2022 · 2 comments · Fixed by #141545
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml v8.5.0

Comments

@walterra
Copy link
Contributor

Kibana version: 8.4.0 BC

Describe the bug:

On initial render, the styles for the brushing component for the baseline and deviation time range don't get applied correctly. The brush handles don't have rounded corners and there's no gap between the brush handlers and badge labels:

image

Only a rerender, for example triggered by resize the browser window, applies the correct styles:

image

There are cases where running the analysis will trigger a resize because the analysis results table makes the page higher and dynamic scrollbars showing up trigger a resize. In this case the brushes would show up briefly as unstyled and then switch to the styles version:

aiops-brush-styling-issue-0001

Expected behavior:

The brushes should be styled correctly right from the start.

@walterra walterra added bug Fixes for quality problems that affect the customer experience :ml v8.5.0 labels Aug 17, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@walterra walterra added the Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis label Aug 17, 2022
@alvarezmelissa87
Copy link
Contributor

Doing some testing to work out what's causing this bug and found that when there are no results and the spike analysis table isn't rendered the brush style is never applied:

image

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 Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml v8.5.0
Projects
None yet
3 participants