Azure单页Web应用SignalR及Redis缓存背板日志技术咨询

Hey there! Let's walk through how to get visibility into both your SignalR logs and Azure Redis Cache backplane logs for your scaled Angular app. I’ve troubleshot similar setups before, so here’s a breakdown of what you need to know:

Whether you’re debugging connection issues, message delivery failures, or scaling quirks, configuring SignalR logs is key to getting actionable insights. Here’s how to set it up:

• Enable server-side ASP.NET Core logging
  Your backend uses ASP.NET Core’s built-in logging system—you just need to configure it to capture SignalR-specific events. In your app’s startup code (either Program.cs or Startup.cs, depending on your .NET Core version), add logging providers and set appropriate log levels:

  services.AddLogging(logging =>
  {
      logging.AddConsole(); // Outputs logs to console (useful for local dev)
      logging.AddDebug(); // Sends logs to debug tools
      // Set minimum level for all logs, or fine-tune for SignalR categories
      logging.SetMinimumLevel(LogLevel.Debug);
      // Filter logs specifically for SignalR and its underlying connections
      logging.AddFilter("Microsoft.AspNetCore.SignalR", LogLevel.Debug);
      logging.AddFilter("Microsoft.AspNetCore.Http.Connections", LogLevel.Debug);
  });
  

  This will capture events like connection handshakes, message broadcasts, and error conditions.

• Capture client-side (Angular) SignalR logs
  Don’t overlook your Angular frontend—client-side logs can reveal issues like dropped connections or failed message reception. When initializing your HubConnection, enable logging:

  import { HubConnectionBuilder, LogLevel } from '@aspnet/signalr-client';
  
  const connection = new HubConnectionBuilder()
    .withUrl('/your-hub-endpoint')
    .configureLogging(LogLevel.Trace) // Use Trace/Debug for detailed logs, Info/Warn for production
    .build();
  

  These logs will show up in your browser’s developer console, so you can spot when a client connects, disconnects, or misses a broadcast.

• Centralize logs with Azure Application Insights
  For production environments, send all SignalR logs to Azure Application Insights for unified monitoring. Add the Microsoft.ApplicationInsights.AspNetCore NuGet package, then configure it in your startup code. Once set up, you can use the Logs section in App Insights to query SignalR events with Kusto queries, like:

  traces | where Category == "Microsoft.AspNetCore.SignalR" and SeverityLevel == 2 // Filter for warnings/errors
  

Since you’re using Redis as a SignalR backplane, you need visibility into two layers: Redis itself, and the SignalR-Redis integration.

• Monitor Azure Redis Cache native logs
  In the Azure Portal, navigate to your Redis Cache resource, then go to Diagnostic Settings. Enable log collection and choose where to send logs (Log Analytics Workspace, Storage Account, or Event Hub). The key logs to watch for are:

  • RedisCommands: Tracks all Redis commands executed, including the PUBLISH/SUBSCRIBE operations the SignalR backplane uses to broadcast messages across instances.
  • RedisConnections: Shows connection attempts, disconnections, and errors between your app instances and Redis.

• Enable SignalR Redis backplane-specific logs
  The Microsoft.AspNetCore.SignalR.Redis package has its own log category. Add a filter to your ASP.NET Core logging configuration to capture these:

  logging.AddFilter("Microsoft.AspNetCore.SignalR.Redis", LogLevel.Debug);
  

  This will log events like when a message is published to the backplane, when a backplane connection is established, or if there’s a failure to communicate with Redis—critical for troubleshooting why broadcasts aren’t reaching all app instances.

• Troubleshooting tips with logs

  • If some clients aren’t receiving broadcast messages: Check the SignalR Redis logs for "Failed to publish message" errors, and verify Redis connection logs don’t show unexpected disconnections.
  • If scaling causes message delays: Use Redis’s RedisCommands logs to check if PUBLISH commands are executing quickly, and cross-reference with SignalR server logs to confirm messages are being picked up by all instances.

• Adjust log levels for production: Avoid using Trace or Debug levels in production—they generate too much noise. Stick to Info, Warn, and Error unless you’re actively troubleshooting.
• Filter logs strategically: Use log categories to narrow down to the exact component you’re debugging (e.g., only Microsoft.AspNetCore.SignalR.Redis when troubleshooting backplane issues).
• Correlate logs: Use request IDs or connection IDs to trace a single client’s journey across server logs, backplane logs, and client logs.

内容的提问来源于stack exchange，提问作者user8559109