Skip to main content

Asset Health and Diagnostics

Summary​

This page describes the three runtime signals the asset-service exposes — a liveness health endpoint, a service-information endpoint, and a tenant-scoped health-data endpoint — and states precisely what each proves and what it does not. Notably, no readiness or dependency health checks are registered, so a healthy liveness result does not imply that the database, broker, or downstream services are reachable.

Audience​

  • DevOps engineers wiring health probes.
  • Support and QA engineers triaging availability.
  • Solution architects assessing observability coverage.

Reference Content​

Signals and meaning​

SignalSourceProvesDoes NOT prove
/healthMapHealthChecks (default)Process is up and serving (liveness)No dependency health; no readiness; no DB/broker/downstream reachability
Service-info endpointMapHrSuitServiceInfoBasic reachability; returns service metadata + correlation idNo dependency health; no data correctness
/asset/health-dataNative asset endpointTenant data presence via live DB counts (assets, available, requested, issued, returned, retired, assignment-history, documents) plus a seeded flag and stage "foundation"Not a dependency/readiness probe; tenant-scoped, not role-gated

Readiness gap​

No readiness or dependency checks are registered. Orchestration probes that need dependency assurance cannot rely on /health for that purpose. Adding readiness checks is not implemented in source; treat dependency-aware readiness as Requires confirmation.

Diagnostic flow​

Access and tenancy notes​

The health-data endpoint performs live database counts and is tenant-scoped rather than role-gated, consistent with the private-mesh anonymous posture. It reflects data presence for the calling tenant only.

Source References​

  • microservices/src/asset-service/Program.cs
  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs

See Also​

Keywords​

asset health, diagnostics, readiness, liveness, tenant health-data

Revision Information​

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