Can I see a log of the 20k Signal R messages my dev app has used?

asked 2020-09-20T21:39:17.503+00:00
Caleb 1 Reputation point

I am in the middle of building a very small Blazor (server) application. I published it to Azure yesterday and today it died. "Service returned handshake error: Maximum message count limit reached: 20000"
My understand is that Blazor is particularly hungry with Signal R but these numbers would mean even the "Standard" signal R tier wouldn't manage for even a hello world Blazor app.

To be able to sell this solution to mu clients I have to make it work and be affordable. Can I see a log of the 20k messages sent? Is there a trick with the new Blazor apps when using them on Azure?

Thanks
Caleb

Azure SignalR Service
Azure SignalR Service
An Azure service that is used for adding real-time communications to web applications.
70 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. answered 2020-09-20T22:14:47.57+00:00
    Caleb 1 Reputation point

    I couldn't see the logs without paying for another service (that I could find) but I could see that the 20k of requests all came in at the same time. I created a new Signal r service clicked around the app and it died within a minute. Sync Fusion Tree View Blazor control, bound to a tree with around 1000 nodes was the culprit.

    No comments

  2. answered 2020-09-21T06:31:39.403+00:00
    SnehaAgrawal-MSFT 11,091 Reputation points Microsoft Employee

    Thanks for asking question! You may refer to this tutorial on resource logs for Azure SignalR Service are, how to set them up, and how to troubleshoot with them.

    To add to this for the SignalR resource in a free tier instance has a message limit of 20000 per day.

    Please check below document on how messages are counted in SignalR service:
    https://learn.microsoft.com/en-us/azure/azure-signalr/signalr-concept-messages-and-connections

    If large messages split into smaller ones and counted as multiple messages, In this case connections gets throttled.

    If the message count is expected, then the only solution is to scale the instance to Standard tier which doesn’t have a hard message count limit.

    Incase issue persists, please send us an email to AzCommunity[at]Microsoft[dot]com referencing this issue.