Darling is the headless, centralized edition of Performance Monitor: a 24/7 service (a Windows service, or Linux with systemd or Docker Compose) that collects from your SQL Servers into a central PostgreSQL (optionally TimescaleDB) store, plus a detached desktop viewer that reads that store. No desktop app has to stay open for collection to happen, and every viewer seat reads the same central data.
Running an install day to day? Running Darling day to day has the steps to add or remove a server, change a password, rotate a token, pause collection, upgrade and uninstall.
It runs the same monitoring brain as the Lite edition — one shared codebase, two storage engines:
PerformanceMonitor.Collectorsowns every collector definition (more than 40 for SQL Server and more than 25 for PostgreSQL): the exact query sent to monitored servers, the result-row mappings, the delta rules, the default cadences and retention horizons, and the ignored-wait-types list. Lite writes those rows to DuckDB; Darling writes the same rows to PostgreSQL via binary COPY. Each definition declares which engine it targets, and a collector never runs against the other one — see PostgreSQL targets.PerformanceMonitor.Alertingowns the shared alert engine — the same thresholds, edge-trigger gates, cooldowns, and dedup fingerprints Lite uses.- The analysis/recommendations pipeline (the same inference engine behind both apps' Recommendations tabs and the
analyze_serverMCP tool) runs on a schedule inside the service.
A collector, alert, or analysis change lands once in the shared libraries and both editions get it. A Darling install monitoring a server even derives the same server_id Lite would for that server, because the identity rule (host[:database][:RO], hashed) is shared too.
| Lite | Darling | |
|---|---|---|
| Collection runs | While the desktop app is open (or in the tray) | 24/7 as a Windows service, or on Linux with systemd or Docker Compose |
| Data lives | Locally per seat (DuckDB + Parquet) | Centrally (PostgreSQL / TimescaleDB) |
| Execution plans | Not stored (fetched live when you view a query) | Captured and stored, TOAST-compressed (capturePlans, default on) |
| Viewers | The app is the viewer | Any number of viewer seats read the central store |
| Setup | Download and run | On Windows, extract the release zip and run install-darling.ps1 (on Linux, see Run on Linux). The shipped default is the bundled store (managed mode), so you provision no database. To use your own PostgreSQL, provision it and set its connection string. |
| Best for | Quick triage, consultants, a handful of servers | Always-on team monitoring, larger estates, one shared store |
| Configuration | Settings UI | darling.json seeds the first start. After that, the Viewer edits servers, alert settings and notification routes in the store. The web dashboard's Admin page edits a server in place and the agent channel of a notification route, for a sign-in that can make changes. Its Alert Settings tab is read-only. |
Nothing is installed on the monitored SQL Servers by either edition beyond three lightweight Extended Events ring-buffer sessions and, when it is unset, a one-time blocked process threshold bootstrap (see What the Service Does on Monitored Servers).
Installing on Windows? Follow
docs/darling/install.md. It is the ordered path from a downloaded zip to a working install, with a proof point at every step.Installing on Linux, or turning on the web dashboard? Read
docs/darling-quick-start.md.
The install reference that was here moved to these pages:
- Install Darling: prerequisites,
darling.json, the pre-flight, the Windows service, the install location, the service account, building from source and the CET error. - The Darling quick start: Docker Compose and systemd on Linux. The container runs as user 1654; see Container user before upgrading an install that ran as root.
- Running Darling day to day: upgrade and roll back.
- Darling and your monitored servers: what the service does on each server, its Extended Events sessions and the permissions it needs.
The headings below keep the old links working.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to The command line reference.
This section moved to the Darling quick start.
This section moved to Install Darling.
This section moved to Running Darling day to day.
This section moved to Running Darling day to day.
This section moved to Running Darling day to day.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to Install Darling.
This section moved to Darling and your monitored servers.
This section moved to Darling and your monitored servers.
This section moved to Darling and your monitored servers.
This section covered every block of darling.json and the collector settings. It moved to these pages:
- Configuration Reference: where each setting lives,
postgres,servers, the PostgreSQL actions, the per-server plan options,peers,heartbeatandreads. - Alert and notification settings:
alerts,analysis,smtp,webhooksand the notification routes. - Agents and alert sources: hand an alert to your own agent, practice requests, the export of judged cases, and the logins for systems that send alerts.
- MCP configuration: the
mcpblock. - Web dashboard configuration: the
webblock. - Collector schedules and switches: why there are no schedule settings, and the verbs and tools that change a collector.
The headings below keep the old links working.
This section moved to Configuration Reference.
This section moved to Configuration Reference.
This section moved to Configuration Reference.
This section moved to Configuration Reference.
This section moved to Configuration Reference.
This section moved to Alert and notification settings.
This section moved to Alert and notification settings.
This section moved to Alert and notification settings.
This section moved to Agents and alert sources.
This section moved to MCP configuration.
This section moved to Web dashboard configuration.
This section moved to Configuration Reference.
This section moved to Collector schedules and switches.
This section moved to Collector schedules and switches.
This section moved to Collector schedules and switches.
This section moved to Collector schedules and switches.
This section moved to Agents and alert sources.
This section moved to Agents and alert sources.
This section covered PostgreSQL servers as monitored targets. It moved to PostgreSQL Targets.
This section moved to PostgreSQL Targets.
This section moved to PostgreSQL Targets.
This section moved to Operations. It covered the store, TimescaleDB, the background workers, retention, the logs, the Viewer, restarts and how to watch the service from outside.
This section moved to Operations.
This section moved to Operations.
This section moved to Operations.
This section moved to Operations.
This section moved to Operations.
This section moved to Security and agent changes.
This section covered a viewer seat on another machine. It moved to The WPF viewer.
This section moved to The WPF viewer.
This section moved to The WPF viewer.
This section moved to Darling troubleshooting.
This section listed the fixed cadences of the service. It moved to Running Darling day to day.
This section covered the store that the service runs for itself in managed mode. It moved to Managed Bundled PostgreSQL.
This section moved to Security and agent changes.
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Opt-in Network Endpoints (LAN).
This section moved to Security and agent changes.
This section covered a threshold value for one server or one database. It moved to Alerts & Notifications.