Asset Management Operations Documentation
Summary
Complete Draft operational documentation for the asset-service runtime: startup and middleware, configuration boundaries, health and diagnostics, structured logging and correlation, audit and timeline operations, the transactional outbox and relay, the workflow, document, and notification integrations, the gateway and compatibility surface, migration and backfill boundaries, smoke testing, and the verified limits of recovery, monitoring, and ownership.
Audience
Operations and DevOps engineers, backend engineers, support, architecture, security reviewers, QA, and product owners.
Overview
Asset-service is an ASP.NET Core (net8.0) minimal-API service. Startup registers observability, shared messaging, the EF Core context, tenant context, repositories and writers, the workflow and document clients, the compatibility layer, and the outbox relay hosted service. In Development it auto-migrates and seeds. The service exposes a health endpoint, a service-information endpoint, and a tenant-scoped health-data endpoint.
Operationally, asset lifecycle changes are written transactionally with audit, timeline, and outbox rows; the outbox relay publishes asynchronously through the shared event bus. Workflow and document interactions are HTTP; notification is a downstream event consumer. The gateway is a reverse proxy with a feature-flagged asset compatibility slice.
The runtime is classified Transitional: the service is functional and observable, but production ownership, monitoring/alerting policy, recovery runbooks, retention governance, and the compatibility retirement plan require confirmation.
Documentation map
- Operations Overview, Runtime and Startup, Configuration Boundaries, and Health and Diagnostics
- Logging, Correlation, and Tracing, Audit and Timeline Operations, and Outbox and Messaging Operations
- Workflow, Document, Notification, and Gateway and Compatibility operations
- Migration and Backfill Boundaries, Smoke Testing, Recovery and Rollback, and Monitoring and Alerting
- Operational Checklist, Escalation and Ownership, and Operational Limitations
Requires confirmation
Production migration ownership, monitoring/alerting policy, on-call ownership, recovery runbooks, retention governance, and compatibility retirement require confirmation.
Source References
microservices/src/asset-service/Program.csmicroservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/scripts/smoke-asset.ps1
Related Articles
See Also
Keywords
- Asset operations
- Runtime
- Outbox operations
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly