Skip to content

Features

chmonitor is organized around the operational questions you answer while running a ClickHouse cluster. Each feature maps to one or more routes in the UI and a feature id you can use to control access or disable it.

All features are public and enabled by default. You only configure what you want to restrict or turn off.

FeatureWhat it answersFeature idPage
OverviewIs my cluster healthy right now?overviewOverview
Query MonitoringWhat queries are running or slow?queriesQuery Monitoring
Tables & StorageHow big are my tables? Where is disk going?tablesTables & Storage
Data ExplorerWhat columns/dependencies does this table have?tablesData Explorer
Merges & OperationsAre merges/mutations keeping up?operationsMerges & Operations
Clusters & ReplicationIs replication lagging? Are replicas healthy?clusterClusters & Replication
Metrics & ProfilerWhat are the server’s CPU/memory/IO metrics?metricsMetrics & Profiler
InsightsWhat patterns or anomalies does the AI surface?insightsInsights
Health & AlertingAre there active alerts?healthHealth & Alerting
Security & AuditWho is accessing ClickHouse and how?securitySecurity & Audit
LogsWhat did the server log?logsLogs
DashboardCustom pinned metrics viewdashboardDashboard
AI AgentNatural language questions about my clusteragentAI Agent
MCP ServerClickHouse monitoring tools for AI clientsmcpMCP Server
PeerDBPeerDB replication pipeline statuspeerdbPeerDB
Browser ConnectionsPersonal ad-hoc connections stored in the browserBrowser Connections
ActionsRow-level actions across data pages (kill query, optimize, etc.)actions
SettingsIn-app settings and configurationsettingsSettings
AuthenticationWho can sign in and what each visitor may accessAuthentication

Disable or restrict any feature with environment variables:

Terminal window
## Disable a feature entirely
CHM_FEATURE_AGENT_ENABLED=false
## Require authentication for a feature
CHM_FEATURE_AGENT_ACCESS=authenticated
## Restrict multiple features at once
CHM_AUTH_REQUIRED_FEATURES=agent,mcp,settings,actions
## Disable multiple features at once
CHM_DISABLED_FEATURES=peerdb,browser-connections

Or use a config file for complex setups:

Terminal window
CHM_CONFIG_FILE=/etc/clickhouse-monitor/config.toml
[features.agent]
access = "authenticated"
[features.mcp]
access = "authenticated"
[features.peerdb]
enabled = false

See Feature Permissions for the full reference.