-
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
[APM] Correlations polish #85116
[APM] Correlations polish #85116
Conversation
Pinging @elastic/apm-ui (Team:apm) |
d6496a4
to
06f4be9
Compare
x-pack/plugins/apm/public/components/app/Correlations/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/Correlations/SignificantTermsTable.tsx
Outdated
Show resolved
Hide resolved
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.
Seeing as this is an experimental feature, I'd rather just get these fixes in. I'm a bit puzzled by the addition of the customize feature (which makes it harder to pull it out once added). @nehaduggal do you have any feedback on the Customize functionality?
Additionally, shouldn't service.version
be one of the default fields that we search for?
Right now there is a hardcoded list of fields. That doesn't work well (especially for user defined fields like labels), so we need a way for users to specify which fields they want analysed. This was the simplest approach I could think of. I'm open to other approaches. I don't think it's hard to pull out. This is an experimental feature - we can do anything we want. Even pull the entire feature and never ship it. |
<EuiFlexItem> | ||
<SignificantTermsTable | ||
cardinalityColumnName="# of slow 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.
Are we adding i18n at this stage?
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 thought about it and opted not to. There's a good chance that all of the copy will be changed anyway (I made all of it up) - so translators will have to do this twice. Not sure what the official guidelines around experimental features are.
@elasticmachine merge upstream |
jenkins run the e2e |
1 similar comment
jenkins run the e2e |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
Distributable file count
History
To update your PR or re-run it, just comment with: |
jenkins run the e2e |
Closes #84863
cc @formgeist