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.

Sign up for GitHub

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

Jump to bottom

[APM] Consider using stats agg instead of sum and avg #94094

Closed
smith opened this issue Mar 9, 2021 · 2 comments
Closed

[APM] Consider using stats agg instead of sum and avg #94094

smith opened this issue Mar 9, 2021 · 2 comments
Labels
apm:performance APM UI - Performance Work Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture

Comments

@smith
Copy link
Contributor

smith commented Mar 9, 2021

Using a stats aggregation may have performance and maintainability benefits where we use sum and avg now. Investigate if this is an improvement and implement it if so.

This is a follow-up from #84661.
@smith smith added the Team:APM All issues that need APM UI Team support label Mar 9, 2021
@elasticmachine
Copy link
Contributor

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

@smith smith mentioned this issue Mar 9, 2021
Closed
7 tasks
@sorenlouv sorenlouv added [zube]: Inbox apm:performance APM UI - Performance Work and removed [zube]: Inbox labels Mar 10, 2021
@sorenlouv sorenlouv added the technical debt Improvement of the software architecture and operational architecture label Jun 21, 2021
@sorenlouv
Copy link
Member

We now have transaction.duration.summary so i don't believe this is relevant anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
apm:performance APM UI - Performance Work Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@smith @sorenlouv @elasticmachine