-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] DF Analytics jobs list: improve job details analysis stats view in expanded row #76196
[ML] DF Analytics jobs list: improve job details analysis stats view in expanded row #76196
Conversation
Pinging @elastic/ml-ui (:ml) |
c872312
to
2030a0b
Compare
const tabs = [ | ||
{ | ||
id: 'ml-analytics-job-details', | ||
name: i18n.translate('xpack.ml.dataframe.analyticsList.expandedRow.tabs.jobSettingsLabel', { | ||
defaultMessage: 'Job details', | ||
}), | ||
content: <ExpandedRowDetailsPane sections={[state, progress, stats]} />, | ||
content: <ExpandedRowDetailsPane sections={sections} />, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is too much information in the 'Job details' tab now. Maybe the content on the Stats and Analysis Stats sections should be moved out onto a new 'Stats' tab?
This would make it consistent with the Models list, which has a Stats tab in the expanded row.
The create_time
and model_memory_limit
seem to belong more on a 'Config' type panel than in 'Stats' but moving them out might be outside the scope of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peteharverson - good call. Added the tab in 246f84299a57803af286499cab2f48c81f6be17a and updated the PR description. This is ready for a final look when you get a chance. cc @jgowdyelastic
description: getItemDescription(analysisStatsValues.timing_stats), | ||
}, | ||
...Object.entries( | ||
analysisStatsValues.parameters || analysisStatsValues.hyperparameters |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to confirm, if parameters
is undefined, is hyperparameters
guaranteed to be defined?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be if analysisStatsValues
is defined - which we check for earlier on. I'll go ahead and add a final option in case both are undefined just to be safe, though 👍
246f842
to
00417eb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested latest edits and LGTM.
For the future we should look to try and standardize the naming and content of the stats tabs across anomaly detection jobs, DFA jobs and models, and transforms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Build SucceededBuild metricsasync chunks size
History
To update your PR or re-run it, just comment with: |
…in expanded row (elastic#76196) * move analysis stats to own section in expanded row * fix type errors * move stats to separate tab in expanded row * handle parameters and hyperparameters not defined
Summary
Fixes #75649
Moves the job's analysis stats info into a separate
Job stats
tab in the expanded row.Details tab:
For failed/running jobs with no analysis stats yet:
Checklist
Delete any items that are not applicable to this PR.