[APM] Investigate impact on span/transaction metrics when storing paths #82598
Labels
Team:APM
All issues that need APM UI Team support
technical debt
Improvement of the software architecture and operational architecture
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.
The text was updated successfully, but these errors were encountered: