Closed caalador closed 2 years ago
With #29 and #36 we now update root span names to contain the route that the user is on.
In addition we can consider classifying requests depending on what operation / action was processed in the request, for example handling events, page load, navigation. Depending on the operation it would be possible to add more information to the span, for example the event type for events. Since monitoring tools use the span name as a grouping mechanism we do not want to provide too much information in the name, as that would explode the number of groups. We need to find a good treshold between number of different span names / groups, and providing some helpful information in the span name for the user.
Closing issue as we already have handling for updating the rootspan
We should have a way to update the main span name to reflect the action instead of only showing the url which is quite static for a single page application and makes it hard to see what happens when most have a name like
/