Asset Monitoring and Alerting
Summary
This page states plainly what monitoring and alerting exist for the asset-service. The service emits structured logs and distributed traces, so telemetry is produced. However, no metrics pipeline, no dashboards, no alert thresholds, no service-level objectives, and no on-call policy were found in source. Operators should treat monitoring and alerting as not yet established and plan accordingly.
Audience
- DevOps engineers planning observability.
- Solution architects assessing production readiness.
- Support engineers understanding what will and will not surface automatically.
Reference Content
What exists (verified)
| Capability | Status |
|---|---|
| Structured JSON logging | Present |
| Distributed tracing (ASP.NET Core + HttpClient) | Present |
| Optional trace exporters (console, OTLP) | Config-gated |
Telemetry is emitted, but consuming and observing it depends on externally configured collectors, which are Requires confirmation per environment.
What does not exist (verified absences)
- No metrics pipeline is configured.
- No dashboards are defined in source.
- No alert thresholds are defined.
- No service-level objectives (SLOs) are defined.
- No on-call policy is defined.
Operational implication
Because no alerting exists, failure conditions — for example, a growing count of Failed outbox rows, broker unavailability, or downstream service outages — will not raise an automatic alert. Detection currently depends on manual inspection through the diagnostics endpoints and logs. Establishing thresholds, dashboards, and on-call policy is Requires confirmation and is not asserted here.
Source References
microservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/asset-service/Program.csmicroservices/src/asset-service/Messaging/OutboxRelayHostedService.cs
Related Articles
See Also
Keywords
asset monitoring, alerting, telemetry, no dashboards, verified absence
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly