Health check
Startup health check on the Log10x MCP installation. Returns a markdown report with pass / warn / fail per check and remediation hints. Checks never block — missing components produce warnings with what to do about it.
Example
"health check"
✓ Environment config valid (
LOG10X_API_KEY,LOG10X_ENV_ID) ✓prometheus.log10x.comreachable, auth OK ✓ Reporter detected: Cloud, edge reporter metrics fresh within 8s ✓ Retriever endpoint reachable ⚠ Datadog destination credentials missing — setDD_API_KEYif you need Datadog integration ✓ Paste endpoint reachable ✓ Enrichment labels present for metric correlation ✓ Scale: 101 TB / 7d · 42 services · 3,212 patterns · 33.9M events per pattern. Retriever deployed — historical events past analyzer retention, dropped-event recovery, metric backfill from archive, and sample-reversal verification are in reach.
More to ask
- "health check on staging"
- "check all envs"
- "is the Reporter wired up correctly?"
Prerequisites
No prerequisites.
Tool schema (advanced)
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
environment |
string | no | all | Environment nickname. In multi-env setups, omit to check ALL configured environments; pass a nickname to check only one. |
Probes: environment config validity · prometheus.log10x.com reachability + auth · Reporter detection (Edge / Cloud / none) · Retriever endpoint · Datadog destination credentials · paste endpoint reachability · enrichment labels for metric correlation (only when LOG10X_CUSTOMER_METRICS_URL is set, v1.4+) · scale and capability summary (7d volume, service count, pattern count, events-per-pattern compression, plus the question types the deployed Retriever does or does not unlock).
The underlying MCP tool ID remains log10x_doctor. The label and prompt are user-facing only.