DSM

Appearance

Observability ​

DSM uses DsmMetrics as its metrics SPI instead of coupling the runtime to a specific framework.

Core Signals ​

At minimum the SPI exposes:

  • sync latency
  • cluster size

Additional callbacks cover:

  • authentication failures and replay rejection
  • admission denial and service ID mismatch
  • LWW discards and dropped messages
  • suspected partitions
  • lease acquisition, renewal, transfer, release, and verification
  • fencing rejections
  • backpressure decisions and queue depth

Why The SPI Matters ​

This lets teams map DSM runtime signals into the telemetry stack they already operate, whether that is Micrometer, OpenTelemetry, or a custom in-house adapter.

No-Op Default ​

DsmMetrics.noop() is available when you need a runtime that operates without external metrics wiring.

Practical Pattern ​

Start with a thin adapter that converts DsmMetrics callbacks into counters, timers, and gauges in your existing platform. Add alerts around lease failures, replay rejection, and sustained queue growth.