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

[APM] Sort by Error Rate is not working on Service list page #80473

Closed
cauemarcondes opened this issue Oct 14, 2020 · 1 comment · Fixed by #80764
Closed

[APM] Sort by Error Rate is not working on Service list page #80473

cauemarcondes opened this issue Oct 14, 2020 · 1 comment · Fixed by #80764
Labels
apm:test-plan-regression bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support v7.10.0

Comments

@cauemarcondes
Copy link
Contributor

servicelist-errorrate.gif

@cauemarcondes cauemarcondes added [zube]: Inbox bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support apm:test-plan-regression v7.10.0 labels Oct 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

smith added a commit to smith/kibana that referenced this issue Oct 15, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

Fixes elastic#80473.
smith added a commit that referenced this issue Oct 16, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

Fixes #80473.
@zube zube bot added [zube]: Done and removed [zube]: Inbox labels Oct 16, 2020
smith added a commit to smith/kibana that referenced this issue Oct 16, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

Fixes elastic#80473.
smith added a commit to smith/kibana that referenced this issue Oct 16, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

Fixes elastic#80473.
smith added a commit that referenced this issue Oct 16, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

Fixes #80473.
smith added a commit that referenced this issue Oct 16, 2020
The field was incorrectly labeled `errorsPerMinute` instead of `transactionErrorRate` (probably left over from before when we switched to using error rate.)

Use `-1` for the fallback sort so "N/A" appears after "0%"

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

Successfully merging a pull request may close this issue.

3 participants