-
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] Updated header icons #84760
[APM] Updated header icons #84760
Conversation
@elasticmachine merge upstream |
359bfab
to
47dd1dd
Compare
@cauemarcondes Maybe I misunderstood something, but if I have multiple versions through a selected time range, I imagine those versions would show in the service version fields. And the same goes for instances. |
Alright, I didn't know it. How should we show it if multiple versions are returned? |
Pinging @elastic/apm-ui (Team:apm) |
@cauemarcondes We should just list them out, and since they're time-based perhaps in chronological order, so the most recent first. Additionally, I think you've implemented it using |
x-pack/plugins/apm/public/components/shared/ApmHeader/service_name_header/icon_popover.tsx
Outdated
Show resolved
Hide resolved
@formgeist Which field are you referring to when you say |
Have we considered doing:
I am worried about the amount of open connections we have to ES when loading the overview page. We can't set a priority on searches and we might need more search threads than are available, leading to other searches being queued. |
I have considered that, but the first version of the API was pretty simple, now I see that I'm changing it to have more aggregated values, I'll probably do like you suggested. |
I believe it's the unique number of |
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.
listItems.push({ | ||
title: i18n.translate('xpack.apm.serviceNameHeader.cloud.zone', { | ||
defaultMessage: | ||
'{zones, plural, =0 {Availability zone} one {Availability zone} other {Availability zones}} ', |
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.
What exactly is happening here if there are no availability zones? It looks like it would have an "Availability zone" title with an empty ul
.
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.
If there are no availability zones this section won't show.
This prevents it:
if (!!cloud.availabilityZones?.length) {
listItems.push({ | ||
title: i18n.translate('xpack.apm.serviceNameHeader.cloud.machine', { | ||
defaultMessage: | ||
'{machineTypes, plural, =0{Machine type} one {Machine type} other {Machine types}} ', |
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.
Same question here as with AZs.
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.
Same thing here, if there are no machine types this section won't show.
x-pack/plugins/apm/public/components/app/service_details/service_icons/container_details.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/icon_popover.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/index.test.tsx
Outdated
Show resolved
Hide resolved
x-pack/test/apm_api_integration/basic/tests/services/service_details.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/container_details.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/app/service_details/service_icons/index.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/server/lib/services/get_service_metadata_icons.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/server/lib/services/get_service_metadata_icons.ts
Outdated
Show resolved
Hide resolved
…ndes/kibana into apm-serv-overview-header-icons
x-pack/plugins/apm/public/components/app/service_details/service_icons/icon_popover.tsx
Outdated
Show resolved
Hide resolved
@@ -78,12 +90,9 @@ export function ServiceIcons({ serviceName }: Props) { | |||
}); | |||
} | |||
}, | |||
[isPopoverOpen, serviceName, start, end, uiFilters] | |||
[selectedIconPopover, serviceName, start, end, uiFilters] |
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 the request made every time the popover is opened/closed or only the first time?
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.
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Distributable file count
History
To update your PR or re-run it, just comment with: |
* creating service name header * fixing icons * removing unused api import * fixing some stuff * adding API tests * refactoring some stuff * fixing tests * refactoring some stuff * fixing i18n * reverting * renaming * applying min width * addressing PR comments and adding test * sorting service version * changing sort type to desc * addressing pr comments * changing to show total and not avg * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]>
* creating service name header * fixing icons * removing unused api import * fixing some stuff * adding API tests * refactoring some stuff * fixing tests * refactoring some stuff * fixing i18n * reverting * renaming * applying min width * addressing PR comments and adding test * sorting service version * changing sort type to desc * addressing pr comments * changing to show total and not avg * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
* creating service name header * fixing icons * removing unused api import * fixing some stuff * adding API tests * refactoring some stuff * fixing tests * refactoring some stuff * fixing i18n * reverting * renaming * applying min width * addressing PR comments and adding test * sorting service version * changing sort type to desc * addressing pr comments * changing to show total and not avg * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]>
* creating service name header * fixing icons * removing unused api import * fixing some stuff * adding API tests * refactoring some stuff * fixing tests * refactoring some stuff * fixing i18n * reverting * renaming * applying min width * addressing PR comments and adding test * sorting service version * changing sort type to desc * addressing pr comments * changing to show total and not avg * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
closes #81717
When should we should the container icon?
the only two possible container orchestration will be Docker or Kubernetes
Kubernetes
: I’ll check if there’s anykubernetes
information in the documentDocker
: If there’s nokubernetes
information and there iscontainer
in the document