-
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 custom index name settings, functional tests for APM Latency Correlation. #105200
[ML] Fix custom index name settings, functional tests for APM Latency Correlation. #105200
Conversation
733a971
to
a39dcf8
Compare
Pinging @elastic/ml-ui (:ml) |
Pinging @elastic/apm-ui (Team:apm) |
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.
Functional tests LGTM, just one small nit.
x-pack/test/functional/apps/apm/correlations/latency_correlations.ts
Outdated
Show resolved
Hide resolved
params: SearchServiceParams | ||
getApmIndices: () => Promise<ApmIndicesConfig>, | ||
searchServiceParams: SearchServiceParams, | ||
includeFrozen: boolean |
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.
Is includeFrozen
being used here?
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 re-read the post description and my question is redundant here :) Sorry the noise
) : null} | ||
</div> | ||
{log.length > 0 && displayLog && ( | ||
<EuiAccordion id="accordion1" buttonContent="Log"> |
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.
Does Log
here needs internationalization?
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 translation in 7592578.
Tested the debug mode and I really like it 🎉 . Definitely much more transparent. My only suggestion for a future follow up is to potentially log out the actual cause/error message as well instead of just On a super duper nit note, noticed the background color of the EuiPanel and the EuiCode are not the same, although I'm not sure if that's something worth adjusting. |
Added a fix to display a warning when we get errors in a cross-cluster environment in ecfd6e4. |
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.
The log helper is nice! Just needs an edit on the CCS callout title, but otherwise LGTM
x-pack/plugins/apm/public/components/app/correlations/ml_latency_correlations.tsx
Outdated
Show resolved
Hide resolved
'xpack.apm.correlations.latencyCorrelations.ccsWarningCalloutBody', | ||
{ | ||
defaultMessage: | ||
'Data for the correlation analysis could not be fully retrieved. This feature is only supported for versions 7.14 and above.', |
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.
Minor suggestion to use "later" instead of "above".
'Data for the correlation analysis could not be fully retrieved. This feature is only supported for versions 7.14 and above.', | |
'Data for the correlation analysis could not be fully retrieved. This feature is supported only for 7.14 and later versions.', |
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 42a7cbd.
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 had a couple suggestions but this looks good.
We should plan to move these FTR E2E tests to our Cypress setup.
@@ -72,7 +75,11 @@ export function MlLatencyCorrelations({ onClose }: Props) { | |||
}, | |||
} = useUrlParams(); | |||
|
|||
const location = useLocation(); | |||
const displayLog = location.search.includes('debug=true'); |
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.
Instead of adding this, we should use the existing observability:enableInspectEsQueries
UI setting.
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.
Great suggestion, fixed in 1a63809.
@@ -94,10 +96,19 @@ const clientSearchMock = ( | |||
}; | |||
}; | |||
|
|||
const getApmIndicesMock = async () => | |||
({ | |||
// eslint-disable-next-line |
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 put the name of the rule to be disabled? Something about casing. It's cool if it's disabled but better if you put the name of the rule there.
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 7d04ca3.
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @walterra |
… Correlation. (elastic#105200) Adds first functional tests for APM Latency Correlations code. - Fix: The log log chart's Y axis would only start at 1 by default which hides results for small datasets like the ones used in these tests. Starting the axis at 0 isn't supported to log based ones so we're setting it to just a small value above 0. - Fix: Instead of the hard coded apm-* index we passed on from the client, we now correctly consider APM's custom settings.
… Correlation. (elastic#105200) Adds first functional tests for APM Latency Correlations code. - Fix: The log log chart's Y axis would only start at 1 by default which hides results for small datasets like the ones used in these tests. Starting the axis at 0 isn't supported to log based ones so we're setting it to just a small value above 0. - Fix: Instead of the hard coded apm-* index we passed on from the client, we now correctly consider APM's custom settings.
… Correlation. (#105200) (#106077) Adds first functional tests for APM Latency Correlations code. - Fix: The log log chart's Y axis would only start at 1 by default which hides results for small datasets like the ones used in these tests. Starting the axis at 0 isn't supported to log based ones so we're setting it to just a small value above 0. - Fix: Instead of the hard coded apm-* index we passed on from the client, we now correctly consider APM's custom settings.
… Correlation. (#105200) (#106078) Adds first functional tests for APM Latency Correlations code. - Fix: The log log chart's Y axis would only start at 1 by default which hides results for small datasets like the ones used in these tests. Starting the axis at 0 isn't supported to log based ones so we're setting it to just a small value above 0. - Fix: Instead of the hard coded apm-* index we passed on from the client, we now correctly consider APM's custom settings. Co-authored-by: Kibana Machine <[email protected]>
Summary
Follow up to #99905.
Adds first functional tests for APM Latency Correlations code.
1
by default which hides results for small datasets like the ones used in these tests. Starting the axis at0
isn't supported to log based ones so we're setting it to just a small value above 0.apm-*
index we passed on from the client, we now correctly consider APM's custom settings.Discuss/Questions:
observability:enableInspectEsQueries
in advanced settings, this will output the async service's log we pass on to the client in the flyout.'apm_oss.transactionIndices'
the correct index to query, do we need to consider others?plugin.ts
to pass onincludeFrozen
, we're not making use of it yet though, is this something we want to fix for 7.14 too?