Oliver Kieselbach fc9e9d13e6 backend: keep slow storage successes and count CAS conflicts as a metric (audit F10) ...

The dependency filter dropped every successful storage call and the expected
412/409 outcomes, so storage-side latency and ETag contention were invisible
until a call failed outright (seven days of App Insights held zero storage
dependency rows).

- StorageDependencyFilterProcessor keeps a successful storage call at or above
  2 s and stamps SlowStorage=true; the operation name is on the row, the table
  name is not (the Azure SDK span carries neither URL nor table).
- StorageMetrics wraps TelemetryClient.GetMetric("StorageCasConflict",
  operation, table, outcome): pre-aggregated per minute, bypasses the worker's
  adaptive sampling, null-tolerant for tests.
- The CAS loops report conflicts: session event count, session counter
  reconcile, session store, tenant stats, MCP user/tenant usage.
- TableStorageService keeps its two-argument constructors (Moq matches by
  exact arity); DI resolves the three-argument overload.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-05 22:09:08 +02:00

..

Agent

Remove the Decision Inspector: web subpage, three session read endpoints, renderer deps (D-197)

2026-09-05 04:51:28 +02:00

Backend

backend: keep slow storage successes and count CAS conflicts as a metric (audit F10)

2026-09-05 22:09:08 +02:00

McpServer

Remove the Decision Inspector: web subpage, three session read endpoints, renderer deps (D-197)

2026-09-05 04:51:28 +02:00

Shared

Remove the Decision Inspector: web subpage, three session read endpoints, renderer deps (D-197)

2026-09-05 04:51:28 +02:00

Web

Remove the Decision Inspector: web subpage, three session read endpoints, renderer deps (D-197)

2026-09-05 04:51:28 +02:00