tramai-spring-boot-starter-sovereign-ops-micrometer

Version: 0.6.0
Status: Preview
Role: Micrometer metrics bridge for the sovereign ops audit-outbox worker.

Purpose

This add-on registers a SovereignOpsAuditOutboxWorkerObserverContribution backed by Micrometer, so audit-outbox worker activity shows up in whatever metrics registry your application already exports (Prometheus, OTLP, Datadog, …).

There is no property switch: the contribution is created when Micrometer is on the classpath and a MeterRegistry bean exists. It registers before the ops auto-configuration, so the base starter's composite observer chain includes it, and the recording observer still updates status snapshots alongside the metrics.

What it provides

Type	Role
`MicrometerSovereignOpsAuditOutboxWorkerObserver`	Emits worker metrics to a `MeterRegistry`
`SovereignOpsOutboxMicrometerAutoConfiguration`	Creates the observer contribution (skipped if a bean with that name already exists)

Metrics export is best-effort by design: a failing registry must not break the worker path.

Dependencies

dependencies {
    implementation(platform("dev.tramai:tramai-bom:0.6.0"))
    implementation("dev.tramai:tramai-spring-boot-starter")
    implementation("dev.tramai:tramai-spring-boot-starter-sovereign-ops")
    implementation("dev.tramai:tramai-spring-boot-starter-sovereign-ops-micrometer")
    implementation("io.micrometer:micrometer-registry-prometheus") // your registry of choice
}

tramai:
  sovereign:
    ops:
      outbox:
        worker:
          enabled: true

When to use this add-on

You already scrape or ship Micrometer metrics and want the outbox worker included.
You want worker throughput and failure counters without a dedicated status endpoint.

When NOT to use this add-on

You want spans and tracing rather than metrics: use tramai-spring-boot-starter-sovereign-ops-observability.
You only need a health/status surface: use tramai-spring-boot-starter-sovereign-ops-actuator.
No MeterRegistry is configured — nothing is registered.