Expense Health and Observability

Summary

Expense exposes a standard health signal and a tenant-scoped foundation summary. Shared observability adds common logging/tracing, but Expense-specific metrics and deep dependency checks are not confirmed.

A healthy process signal does not prove migrations, broker delivery, Workflow, Document, Payroll projection, Notification delivery, or gateway routing. Investigations should correlate request outcome, logs/traces, local evidence, outbox state, and downstream consumer evidence.

No Expense-specific dashboard, metric catalog, alert thresholds, cache telemetry, or formal SLO is confirmed.

Requires confirmation

Deep readiness, dependency probes, metrics, dashboards, log retention, trace sampling, and alert ownership require confirmation.

Source References

• microservices/src/expense-service/Program.cs
• microservices/src/expense-service/Api/ExpenseEndpoints.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs

Related Articles

• Expense operations documentation
• Expense troubleshooting
• Expense technical documentation

See Also

• Expense events
• Expense module

Keywords

• Expense operations
• Health and Observability

Revision Information

• Status: Draft
• Last reviewed: 2026-07-16
• Review cycle: Quarterly