In apps that use background services to do things like poll a queue for new messages, the traces view can get filled very quickly with identical-looking activities. The image below is from a sample being built that uses Azure Functions and polls a storage queue every second for changes:
We should consider adopting a UX whereby trace activities from the same resource with the same spans are grouped into a single row and a badge is displayed showing the count. This is similar to what the Chrome/Edge browser tools do in the Console pane for repeated messages:
The collapsed row would be expanded when clicked. In this way it's essentially another example of auto-grouping items in our grid views.
In apps that use background services to do things like poll a queue for new messages, the traces view can get filled very quickly with identical-looking activities. The image below is from a sample being built that uses Azure Functions and polls a storage queue every second for changes:
We should consider adopting a UX whereby trace activities from the same resource with the same spans are grouped into a single row and a badge is displayed showing the count. This is similar to what the Chrome/Edge browser tools do in the Console pane for repeated messages:
The collapsed row would be expanded when clicked. In this way it's essentially another example of auto-grouping items in our grid views.