Skip to content
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

Colour code changes for services within the same transaction #24818

Closed
simitt opened this issue Oct 30, 2018 · 2 comments
Closed

Colour code changes for services within the same transaction #24818

simitt opened this issue Oct 30, 2018 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support

Comments

@simitt
Copy link
Contributor

simitt commented Oct 30, 2018

Select a trace with at least 2 transactions. Select different buckets in the response time distribution and check which services show up and which colour coding they have. Some of the buckets flip the colour coding for services, which is pretty confusing. Afaik the colour coding is random but should be the same between different buckets.

See screenshots for clarification. In both cases opbeans-node is the service where the trace starts. In the first screen shot it is coloured green and listed as second service item. In the second screenshot it is blue and listed as first service item.

screen shot 2018-10-30 at 10 02 28

screen shot 2018-10-30 at 10 02 46

@simitt simitt added the v6.5.0 label Oct 30, 2018
@simitt simitt added bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support labels Oct 30, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@sorenlouv
Copy link
Member

Closed in sorenlouv#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support
Projects
None yet
Development

No branches or pull requests

4 participants