-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Service map health indicators missing for services with camelcase names #68978
Labels
apm:service-maps
Service Map feature in APM
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
v7.8.0
v7.9.0
Comments
ogupte
added
[zube]: In Progress
bug
Fixes for quality problems that affect the customer experience
apm:service-maps
Service Map feature in APM
Team:APM
All issues that need APM UI Team support
v7.8.0
v7.9.0
labels
Jun 12, 2020
Pinging @elastic/apm-ui (Team:apm) |
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 12, 2020
…to ML job group names.
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 12, 2020
…vices (elastic#68979) * Closes elastic#68978 by encoding service names before comparing them to ML job group names. * Code tweak for readbility Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jun 12, 2020
…vices (elastic#68979) * Closes elastic#68978 by encoding service names before comparing them to ML job group names. * Code tweak for readbility Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
apm:service-maps
Service Map feature in APM
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
v7.8.0
v7.9.0
Service maps are not displaying health indicators for services which have ml jobs and anomalies. This is due too the group names being in the ML job being specifically encoded and lowercased during job creation and then failing to match the actual service name.
The text was updated successfully, but these errors were encountered: