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

Service map anomaly indicators #64718

Merged
merged 7 commits into from
May 4, 2020
Merged

Service map anomaly indicators #64718

merged 7 commits into from
May 4, 2020

Conversation

smith
Copy link
Contributor

@smith smith commented Apr 28, 2020

Get an aggregation of the anomaly scores and show style the ring around the node icon.

image

Closes #63574

Copy link
Member

@sorenlouv sorenlouv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@smith smith force-pushed the nls/anomaly-ring branch 3 times, most recently from 6dea6f6 to b17a119 Compare April 30, 2020 22:05
@smith smith marked this pull request as ready for review April 30, 2020 22:10
@smith smith requested a review from a team as a code owner April 30, 2020 22:10
Comment on lines +28 to +31
max_score: Math.max(
previousValue[key]?.max_score ?? 0,
currentValue.max_score.value ?? 0
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we distinguish between a actual score of 0 and an unknown score?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The things we're reducing over should always have a score, but the type allows for it being undefined, so I think it's ok.

@formgeist
Copy link
Contributor

Minor visual (and probably not changed in the code yet) but noticed that the selected state for the node still marks the ring as primary blue. I would like to keep the health indicator when it's either green, yellow or red. If the service does not have a anomaly score, then we can continue to use the grey default state and blue selected state. Just wanted to raise it...

Screenshot 2020-05-04 at 09 54 14

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@smith smith merged commit 63121fb into elastic:master May 4, 2020
@smith smith deleted the nls/anomaly-ring branch May 4, 2020 18:40
smith added a commit to smith/kibana that referenced this pull request May 4, 2020
Get an aggregation of the anomaly scores and show style the ring around the node icon.
smith added a commit that referenced this pull request May 4, 2020
Get an aggregation of the anomaly scores and show style the ring around the node icon.
@cauemarcondes cauemarcondes self-assigned this May 13, 2020
@cauemarcondes
Copy link
Contributor

Tested:

  • Chrome ✅
  • FF ✅
  • Safari ✅

@cauemarcondes cauemarcondes added the apm:test-plan-done Pull request that was successfully tested during the test plan label May 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:test-plan-7.8.0 apm:test-plan-done Pull request that was successfully tested during the test plan release_note:enhancement v7.8.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[APM] Service maps health indicators: Show anomaly score indicator on Service nodes
6 participants