Health Checks Aggregator — Architecture (agents)

Agent intent

Model this service as control-plane visibility, not domain. Its “business rules” are which downstream URL is critical and what percentage unhealthy fails a gate.

Canonical: Architecture — public

Data flow

flowchart LR
  A[Aggregator] -->|HTTP poll| B[Service 1]
  A --> C[Service 2]
  A --> D[UI / API consumers]

Hold "Alt" / "Option" to enable pan & zoom

Dependency injection

Same Base web pattern: MicroserviceRegistrationBase then template registration (e.g. aggregator coordinator). Do not short-circuit health registration without reading repo AGENTS.md.

Failure modes

• False green: downstream returns 200 but wrong body—validate payload expectations in tests.
• Thundering herd: too aggressive polling—tune intervals per ops runbook.

Related (this repo)

• Overview
• Topic hub
• Observability templates

Canonical technical documentation

➜ ConnectSoft.Documentation