Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 0/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 6/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install MCP Health Monitor. Follow https://mcp.popnx.com/i/oaslananka-health-monitor-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server MCP Health Monitor for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "health-monitor": { "command": "npx", "args": [ "-y", "health-monitor-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCP Health Monitor tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"health-monitor": {
"command": "npx",
"args": [
"-y",
"health-monitor-mcp"
]
}
}
}Use MCP Health Monitor and tell me what you can do for me, then show me one thing✓ If Claude says it is using MCP Health Monitor or shows a MCP Health Monitor tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTH_MONITOR_DB Custom path for the SQLite databaseHEALTH_MONITOR_AUTO_CHECK Set to '1' to enable background scheduled checksHEALTH_MONITOR_RETENTION_DAYS Number of days to retain health check historyHEALTH_MONITOR_MAX_CONCURRENCY Maximum concurrent scheduled and interactive server checksGITHUB_TOKEN Optional GitHub token with Actions read access for private repositories and higher API rate limitsGITLAB_TOKEN Optional GitLab token with read access to private projects, pipelines, jobs, and tracesHEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST Comma-separated self-hosted GitLab HTTPS origins allowed for monitoringHEALTH_MONITOR_HTTP_TARGET_ALLOWLIST Comma-separated private HTTP(S) origins allowed only in the full runtime profileDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect MCP Health Monitor yet
MCP Health Monitor runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect MCP Health Monitor
B · Others in Clinics & health that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server MCP Health Monitor for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user health-monitor -- npx -y health-monitor-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCP Health Monitor tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user health-monitor -- npx -y health-monitor-mcpYou should see MCP Health Monitor listed as connected
Use MCP Health Monitor and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using MCP Health Monitor or shows a MCP Health Monitor tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTH_MONITOR_DB Custom path for the SQLite databaseHEALTH_MONITOR_AUTO_CHECK Set to '1' to enable background scheduled checksHEALTH_MONITOR_RETENTION_DAYS Number of days to retain health check historyHEALTH_MONITOR_MAX_CONCURRENCY Maximum concurrent scheduled and interactive server checksGITHUB_TOKEN Optional GitHub token with Actions read access for private repositories and higher API rate limitsGITLAB_TOKEN Optional GitLab token with read access to private projects, pipelines, jobs, and tracesHEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST Comma-separated self-hosted GitLab HTTPS origins allowed for monitoringHEALTH_MONITOR_HTTP_TARGET_ALLOWLIST Comma-separated private HTTP(S) origins allowed only in the full runtime profileDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server MCP Health Monitor for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "health-monitor": { "command": "npx", "args": [ "-y", "health-monitor-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCP Health Monitor tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use MCP Health Monitor and tell me what you can do for me, then show me one thing✓ If Cursor says it is using MCP Health Monitor or shows a MCP Health Monitor tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTH_MONITOR_DB Custom path for the SQLite databaseHEALTH_MONITOR_AUTO_CHECK Set to '1' to enable background scheduled checksHEALTH_MONITOR_RETENTION_DAYS Number of days to retain health check historyHEALTH_MONITOR_MAX_CONCURRENCY Maximum concurrent scheduled and interactive server checksGITHUB_TOKEN Optional GitHub token with Actions read access for private repositories and higher API rate limitsGITLAB_TOKEN Optional GitLab token with read access to private projects, pipelines, jobs, and tracesHEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST Comma-separated self-hosted GitLab HTTPS origins allowed for monitoringHEALTH_MONITOR_HTTP_TARGET_ALLOWLIST Comma-separated private HTTP(S) origins allowed only in the full runtime profileDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server MCP Health Monitor for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "health-monitor": { "type": "stdio", "command": "npx", "args": [ "-y", "health-monitor-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCP Health Monitor tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use MCP Health Monitor and tell me what you can do for me, then show me one thing✓ If VS Code says it is using MCP Health Monitor or shows a MCP Health Monitor tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
HEALTH_MONITOR_DB Custom path for the SQLite databaseHEALTH_MONITOR_AUTO_CHECK Set to '1' to enable background scheduled checksHEALTH_MONITOR_RETENTION_DAYS Number of days to retain health check historyHEALTH_MONITOR_MAX_CONCURRENCY Maximum concurrent scheduled and interactive server checksGITHUB_TOKEN Optional GitHub token with Actions read access for private repositories and higher API rate limitsGITLAB_TOKEN Optional GitLab token with read access to private projects, pipelines, jobs, and tracesHEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST Comma-separated self-hosted GitLab HTTPS origins allowed for monitoringHEALTH_MONITOR_HTTP_TARGET_ALLOWLIST Comma-separated private HTTP(S) origins allowed only in the full runtime profileDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user health-monitor -- npx -y health-monitor-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"health-monitor": {
"command": "npx",
"args": [
"-y",
"health-monitor-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"health-monitor": {
"command": "npx",
"args": [
"-y",
"health-monitor-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"health-monitor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"health-monitor-mcp"
]
}
}
}HEALTH_MONITOR_DB envHEALTH_MONITOR_AUTO_CHECK envHEALTH_MONITOR_RETENTION_DAYS envHEALTH_MONITOR_MAX_CONCURRENCY envGITHUB_TOKEN secret envGITLAB_TOKEN secret envHEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST envHEALTH_MONITOR_HTTP_TARGET_ALLOWLIST envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 21, 2026
The registry name was verified with the GitHub account oaslananka, which owns the repo
No code changes for over a year, or the repo is archived
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for health-monitor-mcp@1.4.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/oaslananka-health-monitor-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 28 days ago, and the latest version (1.4.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
An MCP server that provides CodeScene Code Health analysis tools.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
| This one MCP Health Monitor | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 2/3 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| License | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server, CI workflow, and generic HTTP endpoint monitoring with health history, TLS expiry, assertions, diagnostics, and operational reports.
health-monitor-mcp keeps local registries of MCP servers, GitHub Actions workflows, GitLab pipelines, and generic HTTP endpoints. It performs live checks, records bounded evidence in SQLite, evaluates MCP alert thresholds, and returns JSON or Markdown diagnostics suitable for agents and operators.
Supported target transports:
Azure DevOps monitoring was retired in v1.1.0. GitHub Actions shipped in v1.2.0 and GitLab CI/CD in v1.3.0; generic HTTP/TLS monitoring completes the current multi-provider feature line.
Run the published package noninteractively with Node.js 24:
npx -y health-monitor-mcp --version
Example MCP client configuration:
{
"mcpServers": { "health-monitor": { "command": "npx", "args": ["-y", "health-monitor-mcp"] } } }
| Tool | Purpose | Typical prompt |
|---|---|---|
register_server | Register an MCP target | Register inventory-prod |
check_server | Run one MCP health check | Check inventory-prod now |
register_github_actions | Register a GitHub workflow | Monitor ci.yml in owner/repo |
check_github_actions | Check latest GitHub run and failed job/step diagnostics | Check repo-ci now |
register_gitlab_pipeline | Register a GitLab project pipeline | Monitor group/project on GitLab |
check_gitlab_pipeline | Check latest pipeline and bounded failed-job traces | Check gitlab-ci now |
register_http_target | Register a GET-only HTTP/HTTPS endpoint | Monitor the public health endpoint |
check_http_target | Check response assertions and TLS expiry | Check service-health now |
register_webhook | Register a webhook target for alert delivery | Register alert-webhook for notifications |
test_webhook | Send a test payload and return delivery diagnostics | Test alert-webhook delivery |
check_all | Check all target kinds with bounded concurrency | Check all production targets |
get_uptime | Return MCP uptime and latency history | Show 24h uptime for inventory-prod |
get_dashboard | Return a cross-provider JSON dashboard | Give me a 24h dashboard |
get_report | Return a cross-provider Markdown report | Generate a 24h health report |
list_servers | List registered MCP targets | List monitored MCP servers |
list_github_actions | List registered GitHub workflow targets | List monitored workflows |
list_gitlab_pipelines | List registered GitLab pipeline targets | List monitored GitLab pipelines |
list_http_targets | List registered HTTP targets | List monitored HTTP endpoints |
list_webhooks | List registered webhook targets | List webhook targets |
unregister_server | Remove an MCP target | Stop monitoring local-debugger |
unregister_github_actions | Remove a GitHub target and its history | Stop monitoring repo-ci |
unregister_gitlab_pipeline | Remove a GitLab target and its history | Stop monitoring gitlab-ci |
unregister_http_target | Remove an HTTP target and its history | Stop monitoring service-health |
unregister_webhook | Remove a webhook target and its history | Stop monitoring alert-webhook |
set_alert | Configure MCP health thresholds | Alert if inventory-prod exceeds 500ms |
get_monitor_stats | Inspect cross-provider monitor activity | How many checks are stored? |
Expected configuration mistakes return stable error codes and remediation hints, including SERVER_NOT_FOUND, GITHUB_ACTIONS_TARGET_NOT_FOUND, GITLAB_PIPELINE_TARGET_NOT_FOUND, GITLAB_BASE_URL_NOT_ALLOWED, HTTP_TARGET_NOT_FOUND, HTTP_TARGET_URL_NOT_ALLOWED, NO_SERVERS_REGISTERED, STDIO_DISABLED, STDIO_COMMAND_REJECTED, WEBHOOK_ENCRYPTION_KEY_REQUIRED, WEBHOOK_REGISTRATION_FAILED, and WEBHOOK_NOT_FOUND.
Streamable HTTP:
register_server name="inventory-prod" type="http" url="https://inventory.example.com/mcp" tags=["production","inventory"]
Legacy SSE:
register_server name="legacy-search" type="sse" url="https://search.example.com/sse" tags=["legacy"]
Trusted local stdio:
export HEALTH_MONITOR_ALLOW_STDIO=1
export HEALTH_MONITOR_STDIO_ALLOWLIST=npx,node
register_server name="local-debugger" type="stdio" command="npx" args=["-y","mcp-debug-recorder"] tags=["local"]
The command field must contain one executable only. Put package names and flags in args. Remote-safe runtime profiles always disable stdio.
Public repositories can be checked without authentication. Private repositories and higher API rate limits require a token with Actions read access:
export GITHUB_TOKEN=your-runtime-secret
register_github_actions name="repo-ci" owner="oaslananka" repository="health-monitor-mcp" workflow="ci.yml" branch="main" token_env="GITHUB_TOKEN" tags=["production","ci"]
check_github_actions name="repo-ci" timeout_ms=5000
Only the environment-variable name in token_env is stored. The token value is read at check time and is never written to SQLite, logs, reports, or tool responses.
Public GitLab.com projects can be checked without authentication. Private projects require a token exposed only through the runtime environment:
export GITLAB_TOKEN=your-runtime-secret
register_gitlab_pipeline name="gitlab-ci" project="group/project" ref="main" token_env="GITLAB_TOKEN" tags=["production","ci"]
check_gitlab_pipeline name="gitlab-ci" timeout_ms=5000
GitLab.com is allowed by default. A self-hosted instance must use an HTTPS origin and be explicitly allowed:
export HEALTH_MONITOR_GITLAB_BASE_URL_ALLOWLIST=https://gitlab.internal.example
register_gitlab_pipeline name="private-gitlab" base_url="https://gitlab.internal.example" project="platform/service" token_env="GITLAB_TOKEN"
Only token_env is persisted. Token values, response bodies, and full traces are never stored or returned. Failed-job trace excerpts are range-requested, sanitized, and bounded.
Public HTTP and HTTPS endpoints are allowed by default. The provider sends GET requests only and supports bounded status, header, body-substring, JSON scalar, and TLS-expiry assertions:
register_http_target name="service-health" url="https://status.example.com/health" expected_statuses=[200] header_assertions=[{"name":"x-ready","equals":"yes"}] body_contains=["ready"] json_assertions=[{"path":"status","equals":"ready"}] tls_expiry_days=30 tags=["production","http"]
check_http_target name="service-health" timeout_ms=5000
Private, loopback, link-local, and other non-public addresses are blocked. A trusted private origin is available only in the full runtime profile and must be explicitly listed:
export HEALTH_MONITOR_HTTP_TARGET_ALLOWLIST=https://status.internal.example:8443
Every DNS answer and every redirect destination is revalidated. Responses are capped at 262144 bytes; full response bodies and certificate chains are never stored or returned.
Webhook targets receive alert notifications via HTTPS POST with optional HMAC-SHA256 signing. Secrets are encrypted at rest when HEALTH_MONITOR_WEBHOOK_ENCRYPTION_KEY is configured (32+ characters); otherwise secret registration is rejected.
register_webhook name="alert-webhook" url="https://hooks.example/alerts" secret="webhook-secret" events=["down","alert"] tags=["production","alerts"]
test_webhook name="alert-webhook"
Secrets are never returned in listings or diagnostics—always redacted. Delivery diagnostics include status, latency, HTTP status code, and error message.
check_server name="inventory-prod" timeout_ms=5000
check_all timeout_ms=5000 tags=["production"] get_uptime name="inventory-prod" hours=24 get_dashboard hours=24 include_tool_stats=true get_report hours=24
HEALTH_MONITOR_MAX_CONCURRENCY limits MCP, GitHub Actions, GitLab, and HTTP checks through one shared scheduled and interactive queue. Results preserve MCP-then-GitHub-then-GitLab-then-HTTP registration order even when checks complete out of order.
set_alert name="inventory-prod" max_response_time_ms=500 min_uptime_percent=99 consecutive_failures_before_alert=2
Alert findings are evaluated by check_server, check_all, and get_dashboard. Configure webhook targets with register_webhook to receive alert notifications.
| Variable | Default | Purpose |
|---|---|---|
HEALTH_MONITOR_DB | ~/.mcp-health-monitor/health.db | SQLite database path |
HEALTH_MONITOR_AUTO_CHECK | 0 | Enable scheduled checks with 1 |
HEALTH_MONITOR_RETENTION_DAYS | 30 | Health-history retention |
| HEALTH_MONITOR_MAX_CONCURRENCY