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] Backends UI: Backend landing page #103253

Closed
Tracked by #103098
formgeist opened this issue Jun 24, 2021 · 1 comment · Fixed by #107379
Closed
Tracked by #103098

[APM] Backends UI: Backend landing page #103253

formgeist opened this issue Jun 24, 2021 · 1 comment · Fixed by #107379
Assignees
Labels
apm:dependencies-ui Team:APM All issues that need APM UI Team support v7.15.0

Comments

@formgeist
Copy link
Contributor

Summary

Meta issue: #103098

The backend page will feature an overall performance health view of the backend based on the metrics from all callees. The list of upstream services breaks down the health of the callee services.

The operations breakdown and analysis is not in scope for 7.15 as we're dependent on changes in the agents and server to get span metrics.

Solution

image

Metrics panels

backend-metrics-panel

The three metrics panels at the top are derived from the destination metrics aggregated for the selected backend. Only average aggregations available for latency for these metrics as they don't support histograms.

Upstream services list

upstream-services-list

The list of upstream services will list the immediate 1-step list of callees to the selected backend. For each we will show the actual service health and performance metrics.

@formgeist formgeist added Team:APM All issues that need APM UI Team support v7.15.0 apm:dependencies-ui labels Jun 24, 2021
@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:dependencies-ui Team:APM All issues that need APM UI Team support v7.15.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants