-
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] Fix UI inconsistencies in APM Failed transaction correlations #109187
Conversation
a145372
to
420e183
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.
Overall everything looks great! 👏 Just a few copy additions/changes suggested.
title={i18n.translate( | ||
'xpack.apm.correlations.failedTransactions.helpPopover.title', | ||
{ | ||
defaultMessage: 'Failed transactions correlations', |
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.
defaultMessage: 'Failed transactions correlations', | |
defaultMessage: 'Failed transaction correlations', |
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.
Updated here 6f9ffa1
> | ||
<p> | ||
<FormattedMessage | ||
id="xpack.apm.correlations.failurePopoverBasicExplanation" | ||
id="xpack.apm.correlations.failedTransactions.helpPopover.basicExplanation" | ||
defaultMessage="Correlations help you discover which attributes are contributing to failed transactions." |
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.
defaultMessage="Correlations help you discover which attributes are contributing to failed transactions." | |
defaultMessage="Correlations help you discover which attributes are contributing to failed transactions. Transactions are considered a failure when it returns a status code >= 5xx." |
Just added the description of failed transactions because I figured it might be helpful in this context.
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.
Updated here 6f9ffa1
@@ -132,7 +132,7 @@ export function TransactionDistribution({ | |||
|
|||
return ( | |||
<div data-test-subj="apmTransactionDistributionTabContent"> | |||
<EuiFlexGroup> | |||
<EuiFlexGroup style={{ minHeight: 56 }}> |
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.
Can you explain why this is necessary? Could we use an EUI px var instead?
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.
Added a comment for it here. The small size selection text is causing the width of that title box to be smaller than the other two (which have the help button), so when you navigate between the tabs there's a bit of a "flickering" or shifting of the title/header spacer.
@@ -0,0 +1,38 @@ | |||
/* |
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.
Nit: Suggest to name this file correlations_log.tsx
for consistency.
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.
Renamed here 6f9ffa1
Thanks for caching that. Updated here 84a0514 Latest changes also include:
|
860880d
to
8300462
Compare
}; | ||
}; | ||
|
||
registry.when('quynh on trial license without data', { config: 'trial', archives: [] }, () => { |
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 testing stuff out with your own name I assume :D
registry.when('quynh on trial license without data', { config: 'trial', archives: [] }, () => { | |
registry.when('on trial license without data', { config: 'trial', archives: [] }, () => { |
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.
Fixed in 909e203 😅
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.
Latest changes LGTM
const response = await supertest | ||
.post(`/internal/bsearch`) | ||
.set('kbn-xsrf', 'foo') | ||
.send(reqBody); | ||
|
||
followUpResponse = parseBfetchResponse(response)[0]; |
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.
It looks like you always want to parse the responses made to the /bsearch
endpoint. In that case, what about creating a bfetchClient which takes the request body and returns the (parsed) response?
const response = await supertest | |
.post(`/internal/bsearch`) | |
.set('kbn-xsrf', 'foo') | |
.send(reqBody); | |
followUpResponse = parseBfetchResponse(response)[0]; | |
const {status, response} = await bfetchClient(supertest, reqBody); |
You could also make bFetchClient a service similar to supertestAsApmWriteUser
and then you can call it without specifying supertest
:
const response = await supertest | |
.post(`/internal/bsearch`) | |
.set('kbn-xsrf', 'foo') | |
.send(reqBody); | |
followUpResponse = parseBfetchResponse(response)[0]; | |
const bfetchClient = context.getService('bfetchClient'); | |
const {status, response} = await bfetchClient(reqBody); |
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.
Moved this to an item on the 7.16 meta issue: #109220
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @qn895 |
…lastic#109187) - Show the same empty state in the correlations table - Add "Correlations" title above the table - Add EuiSpacer between the sections before and after progress - Update the copy within the beta badge title=Failed transaction correlations description=Failed transaction correlations is not GA... - Remove s size from the beta badge - Move the help popover to the top of the panel (similar to the Latency correlations tab) - Move the Cancel/Refresh option to the right of the progress bar (similar to the Latency correlations tab) - When the correlation job is running the correlations tab should show a loading state similar to the latency correlations table - Indicate in the table headers Score is sorted by default - Add sortability to both Latency and failed transactions correlations table - Refactor to prevent duplicate code/components like Log, progress bar - Fix alignments of the tab content header (previously navigating from one Trace samples tab to Latency correlation tabs will cause a minor jump in the header, or the titles within the same tab were not the same size ) - Remove the event.outcome as a field candidate (because event.outcome: failure would always be significant in this case) - Shrink the column width for impact (previously it was at 116px) - Added badge for High, medium, low [APM] Correlations: Show impact levels (high, medium, low) as colored badges indicating their severity - Fix license prompt text - Functional tests for the new tab - Make the p value & error rate columns visible only when esInspect mode is enabled
…lastic#109187) - Show the same empty state in the correlations table - Add "Correlations" title above the table - Add EuiSpacer between the sections before and after progress - Update the copy within the beta badge title=Failed transaction correlations description=Failed transaction correlations is not GA... - Remove s size from the beta badge - Move the help popover to the top of the panel (similar to the Latency correlations tab) - Move the Cancel/Refresh option to the right of the progress bar (similar to the Latency correlations tab) - When the correlation job is running the correlations tab should show a loading state similar to the latency correlations table - Indicate in the table headers Score is sorted by default - Add sortability to both Latency and failed transactions correlations table - Refactor to prevent duplicate code/components like Log, progress bar - Fix alignments of the tab content header (previously navigating from one Trace samples tab to Latency correlation tabs will cause a minor jump in the header, or the titles within the same tab were not the same size ) - Remove the event.outcome as a field candidate (because event.outcome: failure would always be significant in this case) - Shrink the column width for impact (previously it was at 116px) - Added badge for High, medium, low [APM] Correlations: Show impact levels (high, medium, low) as colored badges indicating their severity - Fix license prompt text - Functional tests for the new tab - Make the p value & error rate columns visible only when esInspect mode is enabled
…109187) (#109625) - Show the same empty state in the correlations table - Add "Correlations" title above the table - Add EuiSpacer between the sections before and after progress - Update the copy within the beta badge title=Failed transaction correlations description=Failed transaction correlations is not GA... - Remove s size from the beta badge - Move the help popover to the top of the panel (similar to the Latency correlations tab) - Move the Cancel/Refresh option to the right of the progress bar (similar to the Latency correlations tab) - When the correlation job is running the correlations tab should show a loading state similar to the latency correlations table - Indicate in the table headers Score is sorted by default - Add sortability to both Latency and failed transactions correlations table - Refactor to prevent duplicate code/components like Log, progress bar - Fix alignments of the tab content header (previously navigating from one Trace samples tab to Latency correlation tabs will cause a minor jump in the header, or the titles within the same tab were not the same size ) - Remove the event.outcome as a field candidate (because event.outcome: failure would always be significant in this case) - Shrink the column width for impact (previously it was at 116px) - Added badge for High, medium, low [APM] Correlations: Show impact levels (high, medium, low) as colored badges indicating their severity - Fix license prompt text - Functional tests for the new tab - Make the p value & error rate columns visible only when esInspect mode is enabled Co-authored-by: Quynh Nguyen <43350163+qn895@users.noreply.github.com>
…109187) (#109626) - Show the same empty state in the correlations table - Add "Correlations" title above the table - Add EuiSpacer between the sections before and after progress - Update the copy within the beta badge title=Failed transaction correlations description=Failed transaction correlations is not GA... - Remove s size from the beta badge - Move the help popover to the top of the panel (similar to the Latency correlations tab) - Move the Cancel/Refresh option to the right of the progress bar (similar to the Latency correlations tab) - When the correlation job is running the correlations tab should show a loading state similar to the latency correlations table - Indicate in the table headers Score is sorted by default - Add sortability to both Latency and failed transactions correlations table - Refactor to prevent duplicate code/components like Log, progress bar - Fix alignments of the tab content header (previously navigating from one Trace samples tab to Latency correlation tabs will cause a minor jump in the header, or the titles within the same tab were not the same size ) - Remove the event.outcome as a field candidate (because event.outcome: failure would always be significant in this case) - Shrink the column width for impact (previously it was at 116px) - Added badge for High, medium, low [APM] Correlations: Show impact levels (high, medium, low) as colored badges indicating their severity - Fix license prompt text - Functional tests for the new tab - Make the p value & error rate columns visible only when esInspect mode is enabled Co-authored-by: Quynh Nguyen <43350163+qn895@users.noreply.github.com>
Summary
This PR addresses the issues from #109061 / #109093 / #106381
EuiSpacer
between the sections before and after progresstitle=Failed transaction correlations
description=Failed transaction correlations is not GA...
s
size from the beta badgeevent.outcome
as a field candidate (becauseevent.outcome: failure
would always be significant in this case)- [x] Functional tests for the new tab - [x] Make the p value & error rate columns visible only when esInspect mode is enabled
Checklist
Delete any items that are not applicable to this PR.