-
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] Add AWS and Azure icons for additional services #101901
Conversation
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.
LGTM
f4ac2f3
to
9788cb5
Compare
@cauemarcondes Can you review again? Updated the PR with a storybook and additional icons. |
aws: { | ||
servicename: awsIcon, | ||
servicename: 'logoAWS', |
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.
Maybe since you're repeating logoAWS
and logoAzure
multiple times, would be a good idea to create a constant for them.
servicename: 'logoAWS', | |
servicename: LOGO_AWS, |
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.
Would it make sense to invert it like:
servicename: 'logoAWS', | |
servicename: { | |
aws: LOGO_AWS | |
} |
So we'd call <SpanIcon type="servicename" subtype="aws" />
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 the better solution is that EUI exports this as a constant, so it can be used like:
servicename: ICONS.AWS
I've created an issue for this in the eui repo elastic/eui#4877
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, just left two small comments that are up to you if you want to change it or not.
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
|
||
const types = Object.keys(typeIcons); | ||
|
||
storiesOf('shared/span_icon/span_icon', module) |
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.
@sqren we have a story for node icons: https://github.com/smith/kibana/blob/b307cee64e3bee0cb7bcda742c3f94f17d5d8efe/x-pack/plugins/apm/public/components/app/service_map/__stories__/Cytoscape.stories.tsx#L73-L296, so maybe we should delete that one.
Also we should prefer using Component Story Format over the legacy API.
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.
From the Cytoscape story, I can't tell if we are show-casing the span icons (in which case it should just be deleted), or it's meant to show how it looks in the service map, in which case we should keep it.
It also looks like it's showing the agent icons via iconForNode
so seems like it's covering more than the pure "span_icons" story.
Perhaps we can trim the cytoscape story down to not include every icon but just a few important ones.
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.
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.
Closes #96284
Added icons for AWS and Azure services and added storybook for better visibility.