Ir al contenido
Nexus Docs
↑↓Navigate↵SelectescClose

Audit Baseline

Local Compose measurement procedure and baseline for the auth sign-in audit path

Last updated on:

Esta página aún no está disponible en tu idioma.

The audit service exposes Prometheus metrics for persisted events, sealed batches, and published anchors. Use this baseline to record local Compose measurements for the auth sign-in audit path.

Measurement Procedure

Section titled “Measurement Procedure”
  1. Start the dev stack with a short anchor interval:
Terminal window
AUDIT_ANCHOR_INTERVAL_SECS=10 docker compose -f deploy/compose/docker-compose.yml up -d --build

  1. Create and sign in a user through the auth REST API.

  2. Measure these timestamps from the client and backing stores:

  • t0: the client sends POST /api/auth/sign-in.
  • t1: the row is visible in nexus_audit.audit_events.
  • t2: the row has batch_id IS NOT NULL.
  • t3: a meta-root object is visible under nexus-audit-archive/meta-roots/.
  1. Capture audit metrics from http://localhost:14459/metrics when the audit HTTP port is published or from inside the compose network.

Current Local Baseline

Section titled “Current Local Baseline”

The compose-it audit pipeline test exercises the same path and expects:

  • user.signed_in appears in audit_events within 60 seconds.
  • The event is sealed and anchored within 60 seconds when AUDIT_ANCHOR_INTERVAL_SECS=2.
  • nexus-audit-verify verify --archive-path <archive> exits 0 on the copied archive.

These thresholds are deliberately local-dev bounds for the sign-in audit path. They are not production service-level objectives.

See Audit Event Contract for the event/batch/anchor shapes this baseline measures, and Runbook: Audit Verifier Failure if verification does not exit 0.