You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an external visualization tool that lacks the ability to group spans/errors into application actions, without relying on a costly transaction.id join style listing.
If the spans and errors had a transaction.name metadata on it (which should be there as per documentation), that operation would make way less pressure on the Elasticsearch cluster.
The text was updated successfully, but these errors were encountered:
I have an external visualization tool that lacks the ability to group spans/errors into application actions, without relying on a costly
transaction.id
join style listing.If the spans and errors had a
transaction.name
metadata on it (which should be there as per documentation), that operation would make way less pressure on the Elasticsearch cluster.The text was updated successfully, but these errors were encountered: