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] Investigate impact on span/transaction metrics when storing paths #82598

Closed
dgieselaar opened this issue Nov 4, 2020 · 2 comments
Closed
Labels
Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture

Comments

@dgieselaar
Copy link
Member

For elastic/apm#364, we are looking into storing (upstream) paths in span metrics (outgoing) and transaction metrics (incoming). This will increase the amount of metric documents being stored, as they will be unique per upstream.

We should get a better feeling of what the impact will be. We can write a script that walks traces, and generates a unique string for the upstream of a span, so we have an idea about the cardinality of the path hash.

@dgieselaar dgieselaar added the Team:APM All issues that need APM UI Team support label Nov 4, 2020
@elasticmachine
Copy link
Contributor

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

@dgieselaar
Copy link
Member Author

Not planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

No branches or pull requests

4 participants