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

Add error rate chart to overview #82082

Merged
merged 6 commits into from
Nov 2, 2020
Merged

Conversation

smith
Copy link
Contributor

@smith smith commented Oct 29, 2020

Take most of the work directly from #80298 to add the error rate chart to the overview.

Rename the existing chart that's on the transactions overview so it still keeps using the old chart for the time being. We don't want to mix chart types (react-vis + elastic-charts) on the same page becuase the interactions are different. We'll switch the transactions page to use elastic charts in a future PR.

Hide the error rate chart on RUM services.

First step of #81719.

Take most of the work directly from elastic#80298 to add the error rate chart to the overview.

Rename the existing chart that's on the transactions overview so it still keeps using the old chart for the time being. We don't want to mix chart types (react-vis + elastic-charts) on the same page becuase the interactions are different. We'll switch the transactions page to use elastic charts in a future PR.

Hide the error rate chart on RUM services.
@smith smith marked this pull request as ready for review October 30, 2020 00:38
@smith smith requested a review from a team as a code owner October 30, 2020 00:38
@smith smith added v7.11 release_note:skip Skip the PR/issue when compiling release notes v8.0.0 labels Oct 30, 2020
@timroes timroes added v7.11.0 and removed v7.11 labels Oct 30, 2020
@botelastic botelastic bot added the Team:APM All issues that need APM UI Team support label Oct 30, 2020
@elasticmachine
Copy link
Contributor

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

@smith
Copy link
Contributor Author

smith commented Nov 2, 2020

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

@kbn/optimizer bundle module count

id before after diff
apm 1276 1280 +4

async chunks size

id before after diff
apm 3.2MB 3.2MB +7.2KB

History

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

Copy link
Contributor

@cauemarcondes cauemarcondes left a comment

Choose a reason for hiding this comment

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

just a nit comment. LGTM 📈

@smith smith merged commit 2f504a0 into elastic:master Nov 2, 2020
@smith smith deleted the nls/overview-error-rate branch November 2, 2020 16:24
smith added a commit to smith/kibana that referenced this pull request Nov 2, 2020
* Add error rate chart to overview

Take most of the work directly from elastic#80298 to add the error rate chart to the overview.

Rename the existing chart that's on the transactions overview so it still keeps using the old chart for the time being. We don't want to mix chart types (react-vis + elastic-charts) on the same page becuase the interactions are different. We'll switch the transactions page to use elastic charts in a future PR.

Hide the error rate chart on RUM services.
smith added a commit that referenced this pull request Nov 2, 2020
Take most of the work directly from #80298 to add the error rate chart to the overview.

Rename the existing chart that's on the transactions overview so it still keeps using the old chart for the time being. We don't want to mix chart types (react-vis + elastic-charts) on the same page becuase the interactions are different. We'll switch the transactions page to use elastic charts in a future PR.

Hide the error rate chart on RUM services.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team:APM All issues that need APM UI Team support v7.11.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants