Oliver Kieselbach 9e3a2e3708 fix(backend): bound SignalR sends + skip degenerate Azure Monitor range ...

Two hardening fixes surfaced by 48h backend log review:

- AzureMonitorMetricsReader.GetTotalAsync: skip the round-trip when the query range is shorter than 1 minute. The SignalR-quota watcher and the health check both anchor the start of the range to start-of-day, so a call landing on the 00:00 UTC boundary sent from==to and absorbed a daily 400 BadRequest.

- SignalRNotificationService: cap every imperative send (hub-context resolution + SendCoreAsync) at 5s via CancellationTokenSource. Without it a slow/unreachable SignalR endpoint blocks for the SDK HttpClient default of 100s, pinning the calling queue-worker/Task.Run thread. These pushes are observability nudges, never correctness, so fail fast and swallow as before.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-06 09:57:18 +02:00

..

AzureMonitorMetricsReader.cs

fix(backend): bound SignalR sends + skip degenerate Azure Monitor range

2026-06-06 09:57:18 +02:00

AzurePoisonQueueProbe.cs

refactor(queue): extract QueueClientFactory + QueuePollingWorker base (audit D2)

2026-06-05 14:56:41 +02:00

IAzureMonitorMetricsReader.cs

feat(backend/observability): SignalR free-quota watcher with tiered OpsEvents

2026-05-08 18:06:56 +02:00

IPoisonQueueProbe.cs

feat(backend/health): surface async-worker poison queue backlog in /health/detailed

2026-05-11 14:18:38 +02:00