Skip to content

[ML] AIOps: Using no minimum time range by default for pattern analysis#191192

Merged
jgowdyelastic merged 5 commits intoelastic:mainfrom
jgowdyelastic:using-no-minimum-time-range-by-default
Aug 29, 2024
Merged

[ML] AIOps: Using no minimum time range by default for pattern analysis#191192
jgowdyelastic merged 5 commits intoelastic:mainfrom
jgowdyelastic:using-no-minimum-time-range-by-default

Conversation

@jgowdyelastic
Copy link
Member

Changing the default selection from 1 week to No minimum.
For indices with very large doc counts, it is safer not to query a week's worth of data by default, but rather use the time range selected in the time picker.

@jgowdyelastic jgowdyelastic added release_note:enhancement :ml Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis v8.16.0 labels Aug 23, 2024
@jgowdyelastic jgowdyelastic self-assigned this Aug 23, 2024
@jgowdyelastic jgowdyelastic marked this pull request as ready for review August 23, 2024 13:36
@jgowdyelastic jgowdyelastic requested a review from a team as a code owner August 23, 2024 13:36
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

import { i18n } from '@kbn/i18n';
import type { unitOfTime } from 'moment';

export const DEFAULT_MINIMUM_TIME_RANGE_OPTION: MinimumTimeRangeOption = 'No minimum';
Copy link
Contributor

@peteharverson peteharverson Aug 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we could do with some clarification in the UI as to what 'No minimum' means? Possibly some text in the help tooltip, and some text below the 'Minimum time range' field if they have 'No minimum' selected. e.g. does it mean it will search right back to the start of the data in the data view, or just to the start date set in the time picker.

Screenshot 2024-08-23 at 17 18 28

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I agree. I'm not sure what the text should say for the No minimum option.
The time range used will match the time picker ?
No additional time will be added to the range selected ?

@szabosteve do you have any ideas?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgowdyelastic @peteharverson
I'd change the dropdown label to Use selected time.
And the helper text – if needed – could be something like:
The time range you specified using the time selector will be used for the analysis.
What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of changing the label in the dropdown from 'No minimum' to 'Use selected time' (or even 'Use range selected in time picker' to clarify which selected time?).

The only issue with The time range you specified using the time selector will be used for the analysis. for the help text is that it then begs the question of why wouldn't the analysis always used the selected time range? Maybe something along the lines of No additional time be added. ?

Very difficult to explain concisely what this setting relates to!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about the following as the helper text?
No additional time is added to the range you specified with the time selector.

However, if the selector label is changed to Use range specified in time selector or something along these lines, then I don't think a helper text is necessary.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Text updated to:
image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit - I think the form help texts normally end with a .

Copy link
Contributor

@darnautov darnautov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@peteharverson peteharverson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - think it's just worth adding the closing . to the help text.

@kibana-ci
Copy link

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
aiops 632.7KB 633.3KB +626.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @jgowdyelastic

@jgowdyelastic jgowdyelastic merged commit 525d9f6 into elastic:main Aug 29, 2024
@kibanamachine kibanamachine added the backport:skip This PR does not require backporting label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml release_note:enhancement v8.16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants