Skip to main content
Version: 0.15 (unstable)

Monitoring

Network operators can use miden-network-monitor and OpenTelemetry tracing to observe network health, RPC freshness, validator status, prover status, and related infrastructure.

Network Monitor​

miden-network-monitor is an observer and test client. It is not required for block production. Depending on configuration, it can check RPC freshness, validator health, remote prover status, faucet availability, explorer availability, note transport, and end-to-end network transaction flows.

Use the binary help output for the current configuration surface:

miden-network-monitor start --help

Telemetry​

Services export OpenTelemetry traces when an OTLP trace endpoint is configured through the standard OpenTelemetry environment variables.

Set one of:

  • OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
  • OTEL_EXPORTER_OTLP_ENDPOINT

Services register a default OpenTelemetry service name and the miden service namespace. To distinguish multiple instances of the same service, set service.instance.id through OTEL_RESOURCE_ATTRIBUTES.

For example:

OTEL_EXPORTER_OTLP_ENDPOINT=http://collector:4317 \
OTEL_RESOURCE_ATTRIBUTES=service.instance.id=full-node-1 \
miden-node full ...

Other standard OpenTelemetry resource variables, such as OTEL_SERVICE_NAME, can still be used when an operator needs to override the default service identity.