server response time needs to ignore signalr
The average response time metric is not very useful if it is counting signalr persistent connections. I can't filter out these requests in the default dashboard graphs and it's a pain to filter it out in every single graph I create. There needs to be a way to ignore certain patterns from being tracked.
Thank you all for sharing the feedback and upvoting for this feature. It is something being reviewed internally by the team and will be considered in the next wave of planning.
Howard Hoffman commented
We'd like Signal R data to be filtered out of the App Insights default 'Performance' blade query. We often see this dominated by Signal R Reconnects and Ping. While interesting from a "is SignalR healthy / using-WebSockets / etc.' perspective it's not at all interesting from a Performance perspective.
Kristian Williams commented
This is an absolute nightmare for our real time monitoring.
A single SignalR websocket connection active for 15h managed to completely destroyed a days worth of our metric trends.
Even if you don't and support specifically for SignalR, just having a global filter option in the Application Insights settings would be a huge help.
Hi Michael, any updates on this feature?
We are looking to add exclusion filtering capabilities for operational names in our upcoming UX iteration. Please stay tuned and keep up-voting.
-AI Product Team
Mikey Cooper commented
Top 4 in the poorly performing operations list under Performance are SignalR every single time for me:
Makes noise in avg dependency time as well. And total dependency failures when using long-polling. Server Requests. Failed Requests.
Pretty much every chart and list I have to measure worst performers includes SignalR long-polls, pings, reconnects, etc.
Can you please offer a more concrete example? Are you building dashboard graphs by pinning ME blades or by writing Analytics queries?
-AI Product Team