Diagnostics Lab
diagnostics-lab is an experimental ASP.NET Core application for exercising the diagnostics
path without touching a production environment. It is a lab, not a production service.
Current state
The repository is initialized with a src/DiagnosticsLab project containing Chaos,
ControlPlane and wwwroot areas. The deploy, features and tests folders are present
but the repository is not yet a deployed service and has no public contract. Treat this page
as a pointer to the repository, not as an API reference.
Why it exists
Diagnostics are hard to test against a healthy system:
- The interesting states are failures: an unresponsive agent, a stale trace, a control plane that returns an error.
- Reproducing those states in production is unacceptable.
- A lab lets you inject the failure, point the bot or the control plane at it, and verify the card, the status transition and the error text.
Intended use
- Run the lab locally.
- Point a diagnostic bot or an API control-plane client at the lab instead of production.
- Exercise a chaos scenario and confirm the observable behavior: the card, the correlation id, the recorded status and the log line.
- Turn the scenario into an automated test in the lab's
testsproject.
Status and expectations
| Aspect | Status |
|---|---|
| Repository | Initialized |
| Application skeleton | Present (Chaos, ControlPlane, wwwroot) |
| Deployment | None |
| Public API | None |
| Tests | Not yet implemented |
Do not depend on the lab from a production service. When a scenario graduates, move it to the owning service's test suite.