Installing Performance Monitor Darling

Darling web dashboard fleet overview showing four healthy SQL Servers minutes after install

Darling is the headless version of Performance Monitor. It is one Windows service that collects from your SQL Servers into its own bundled PostgreSQL and TimescaleDB store, and serves three ways to look at the data: a web dashboard, a desktop viewer, and an MCP endpoint you can point an AI client at. Nothing gets installed on the servers you monitor. One install watches 5 servers or 500.

This is the full install, start to finish, on a plain Windows Server 2022 VM. Including the part where one of my servers was dead when I installed, because one of yours will be too.

Last checked against Darling 3.11.0 in October 2026. The screenshots come from a fresh 3.11.0 install on a Windows Server 2022 VM that monitors one server, SQL2019, which was up. The story in the text, where one of five servers was down, comes from an earlier run. Where this page and the Darling README on GitHub disagree, the README is right.

Picked Lite? This page is the Darling install, which is a service. Lite is a desktop app with no service and no store to set up. Its steps are under Lite Edition Setup in Getting Started on the landing page: download, install, Add Server. The Lite Install Walkthrough shows each step with screenshots. The Lite README on GitHub has the full detail.

What you need

  • A Windows box for the service. Mine is a small VM named DARLING01. It does not need to be big: the service and its store are light until you point hundreds of servers at it.
  • A Windows that is current on its updates. .NET 10 programs need them to start on a CPU with CET, a hardware protection. Without them the service and the viewer both stop at start with exit code 0x80131506. There is a section on it below.
  • The .NET 10 Runtime and the ASP.NET Core 10 Runtime, both for Windows x64. The ASP.NET Core Hosting Bundle 10 installs the two together. The service needs both even if you never turn on the web dashboard or MCP. install-darling.ps1 checks for them and stops with a message that names what is missing. The viewer folder in the zip also needs the .NET Desktop Runtime 10. Without it the installer only warns, and the viewer shortcuts fail until it is installed. The separate viewer Setup.exe carries its own runtime.
  • A SQL login (or Windows account) with VIEW SERVER STATE and msdb access on each server you want to monitor.

Download and verify

Grab PerformanceMonitorDarling-<version>.zip from the latest release, plus SHA256SUMS.txt from the same page. Do the rest of this page from an elevated PowerShell (Run as administrator), opened in the folder you downloaded to. The next step extracts into Program Files, and only administrators can write there. Then make sure the bits are the bits:

$zip = 'PerformanceMonitorDarling-<version>.zip'    # the file you downloaded
(Get-FileHash -Path $zip -Algorithm SHA256).Hash.ToLower()
Select-String -Path .\SHA256SUMS.txt -SimpleMatch -Pattern $zip

The two hex strings have to match. If they do not, stop and download again.

Extract somewhere the service can live

Extract to C:\Program Files\PerformanceMonitorDarling. That is the documented location, and the one to use.

Expand-Archive -Path $zip -DestinationPath "C:\Program Files\PerformanceMonitorDarling"

Two kinds of folder are wrong, for two different reasons:

  • A folder made directly under C:\, such as C:\PerformanceMonitorDarling (the older documented example). A new folder there inherits Modify for Authenticated Users from the drive root the moment it is extracted. Any local user can then swap a binary before the installer runs a single line, so install-darling.ps1 refuses it. C:\Program Files denies write to ordinary users by default. The refusal has an override, -AcceptWritableExtraction. It is for a dev loop, not for a real install.
  • Your Downloads folder or anywhere under C:\Users, plus a UNC path or a mapped drive. The service runs as an unprivileged virtual account that cannot read your profile, and a service does not share your mapped drives. The installer refuses these too, rather than let you install something that dies on first start.

Check the folder holds PerformanceMonitor.Darling.Service.exe, darling.sample.json, install-darling.ps1, pg-runtime.zip, a wwwroot folder, and a viewer folder with the desktop viewer in it.

Configure darling.json

Copy darling.sample.json to darling.json in the same folder (you are elevated, so Notepad can save into Program Files). The sample is heavily commented and worth reading once, but here is a working config: five servers, the store, the web dashboard, and MCP, all reachable from my LAN. Comments are allowed in the file, so you can keep notes in it. The file is JSONC, not plain JSON, so edit it as text and do not round-trip it through ConvertFrom-Json, which fails on the comments. If there is no darling.json, install-darling.ps1 copies darling.sample.json to darling.json and stops so you can edit it. Edit the file, then run the script again.

{
  // The service runs its own bundled PostgreSQL + TimescaleDB on an
  // uncommon port so it coexists with anything already on the box.
  // The network block exposes the store to the LAN over TLS so the
  // desktop viewer can connect from your workstation, read only.
  "postgres": {
    "managed": true,
    "port": 5641,
    "connectAs": "admin",
    "network": {
      "listen": "192.168.1.205",
      "allowFrom": "192.168.1.0/24",
      "role": "viewer"
    }
  },

  // The servers to monitor. Encrypted passwords come from
  // --encrypt-password, run on this machine (the blob is DPAPI
  // machine-bound, so it only decrypts here).
  "servers": [
    {
      "name": "SQL2016",
      "host": "SQL2016",
      "auth": "sql",
      "username": "sa",
      "encryptedPassword": "AQAAANCMnd8BFdERjHoAwE...",
      "trustServerCertificate": true,
      "encryptMode": "Optional"
    }
    // ...and four more just like it
  ],

  // MCP endpoint: point Claude or another MCP client at
  // http://192.168.1.205:5152 with the bearer token.
  "mcp": {
    "enabled": true,
    "port": 5152,
    "network": {
      "listen": "192.168.1.205",
      "allowFrom": "192.168.1.0/24",
      "encryptedToken": "AQAAANCMnd8BFdERjHoAwE..."
    }
  },

  // Web dashboard: browse to http://192.168.1.205:5153/?token=...
  // from anywhere in the allowed range.
  "web": {
    "enabled": true,
    "port": 5153,
    "network": {
      "listen": "192.168.1.205",
      "allowFrom": "192.168.1.0/24",
      "encryptedToken": "AQAAANCMnd8BFdERjHoAwE..."
    }
  }
}

A few things worth saying about this file.

  • Everything network-facing is off by default. If you leave the network blocks out, the store, MCP, and the dashboard bind loopback only and nothing is exposed. You opt in per endpoint, with a bind address, a CIDR, and a token.
  • The tokens and passwords in the file are encrypted blobs, not plaintext. You make them on the service box:
cd "C:\Program Files\PerformanceMonitorDarling"
Read-Host -Prompt 'password' | .\PerformanceMonitor.Darling.Service.exe --encrypt-password

Paste the output line into the config. Same verb for the SQL password, the web token, and the MCP token. The blobs are machine-bound DPAPI, so a copied darling.json is useless on another box.

  • Integrated auth works too (“auth”: “integrated”), and is the right answer on a domain. My lab VMs are workgroup machines, so SQL auth it is.
  • trustServerCertificate true is for lab boxes with self-signed certs. Production servers with real certificates should leave it false.

Preflight: probe every server first

Before installing anything, the exe can validate the config and connect to every server in it:

cd "C:\Program Files\PerformanceMonitorDarling"
.\PerformanceMonitor.Darling.Service.exe --test-connection
Validating connectivity to 5 server(s)...
  [PASS] SQL2016: SQL major version 13, Enterprise, msdb access: yes
  [PASS] SQL2017: SQL major version 14, Enterprise, msdb access: yes
  [FAIL] SQL2019: A network-related or instance-specific error occurred while establishing
         a connection to SQL Server. The server was not found or was not accessible.
  [PASS] SQL2022: SQL major version 16, Enterprise, msdb access: yes
  [PASS] SQL2025: SQL major version 17, Enterprise, msdb access: yes
One or more servers failed the connection pre-flight (see above).

SQL2019 is dead. I knew that, and I left it in the config on purpose, because this is what real fleets look like: something is always down, and I want the monitor to tell me about it rather than pretend it is not there. It exits non-zero so you can use it as a deployment gate, and each PASS line tells you the version, edition, and whether msdb access works before you commit to anything. This command connects as you, not as the service account. With Windows authentication, a PASS proves the server is reachable and the config is well formed. It does not prove the service account has the grants. The connect lines in the log after install are the real proof.

Install

From the install folder, in the elevated PowerShell you already have:

cd "C:\Program Files\PerformanceMonitorDarling"
.\install-darling.ps1

Before anything else it refuses a folder that ordinary users can write to, which is why the extract step matters. Then it runs the same preflight and stops to ask about SQL2019. I told it to carry on.

Then it does the real work. It registers the Event Log source and creates the service. It locks the install folder, sets the credential file permissions, and opens the scoped firewall rules for whatever your config exposes. Then it starts the service. It does not wait for the first start to finish. The output is worth reading because it explains itself. These are the lines that matter, with the counts and timings left out because they change:

Created service 'PerformanceMonitor Darling' (NT SERVICE virtual account, automatic start).
Locked the install folder: only SYSTEM and Administrators can change what runs from it ...
MCP: opened 'PerformanceMonitor Darling MCP (port 5152)' (TCP 5152, inbound, from 192.168.1.0/24).
web dashboard: opened 'PerformanceMonitor Darling Web (port 5153)' (TCP 5153, inbound, from 192.168.1.0/24).
Done. 2 endpoint(s) exposed on the LAN; their scoped rules are in place.
Service is Running. First start does real work (unpack pg-runtime, initdb, store migration, first collection cycle) - give it ~2 minutes.
Created 'Darling Viewer' shortcuts (2). Pin to taskbar from the Start Menu entry if wanted.
Done.

The installer also creates a local group called PerformanceMonitor Darling Operators, empty, and never adds anyone to it. Add each person who runs the viewer or the CLI without elevation with net localgroup “PerformanceMonitor Darling Operators” DOMAIN\user /add. Until someone is in that group, they cannot run the viewer or the service exe’s command line switches unless they run as administrator.

Points worth noticing. The service runs under a virtual account, never LocalSystem: the bundled PostgreSQL refuses to run with administrative privileges, which is the correct paranoia. The firewall rules are scoped to the CIDR from your config, not opened to the world. And the ACLs on darling.json get re-applied on every service start, so a loosened permission repairs itself.

First start

The first start unpacks the PostgreSQL runtime, initializes the cluster, runs every store migration, and starts collecting. About two minutes on my VM. The installer starts the service and returns without waiting, so give it that time before you look for data. The log at %ProgramData%\PerformanceMonitorDarling\logs tells you the same thing. These are the lines to look for, in this order. The schema version and the counts change with each release, so they are left out:

Postgres store ready (schema v..., ... migration(s) applied)
Least-privilege roles ready (...)
TimescaleDB detected ...
TimescaleDB: .../... collector table(s) are hypertables
PerformanceMonitor Darling collection loop started

The collection loop started line means ready. On the hypertables line, the two numbers must match. After that you see a Connected line for each server that answered. Each sweep then logs a line per collector with the rows it got.

That is a complete time-series store with retention tiers already armed. Nobody has to learn PostgreSQL administration to run this.

If the service stops at start with 0x80131506

On a Windows that is not fully patched, the service and the viewer both stop at start. The exit code is 0x80131506 and stderr shows this:

Fatal error. Your Windows doesn't fully support CET. Please install all available Windows updates.

This is .NET 10 on a CPU with CET. I have seen it on Windows Server 2022 build 20348.1366. The installer recognises that message in its preflight and stops with a plain message instead of asking whether to install anyway. The fix is what the message says: install all available Windows updates and restart.

If you cannot patch yet, there is a stopgap. From an elevated PowerShell, turn off the hardware stack protection for the two Darling programs:

Set-ProcessMitigation -Name PerformanceMonitor.Darling.Service.exe -Disable UserShadowStack
Set-ProcessMitigation -Name PerformanceMonitor.Darling.Viewer.exe -Disable UserShadowStack

That weakens those programs’ protection, so treat it as temporary. The way to undo it once Windows is patched is in the Darling README, in the section on the CET error. It is a registry removal, because Set-ProcessMitigation -Remove did not work on the build I tried.

Open the dashboard

From my workstation, not from the server:

http://192.168.1.205:5153/?token=your-token-here

You present the token once. It gets exchanged for a signed session cookie and stripped from the URL, so it does not sit in your address bar or your history.

Darling web dashboard Fleet Overview with one SQL Server, SQL2019, healthy a few minutes after install

Servers join the wall as their first collection cycle lands, which took a couple of minutes each here. Click one and you get the full drill-down: wait stats, blocking, queries, file I/O, configuration changes, collection health, all of it already accumulating.

Darling web dashboard drill-down for SQL2019 with CPU, threads and memory tiles and the Overview tab

One honest warning from the service log that you should take seriously: without TLS, the token and its cookie cross your network in the clear. The dashboard takes a certificate from your internal CA in the config (a pfx or a PEM pair), or you put a TLS reverse proxy in front of it. On my lab LAN I have not bothered. On yours, bother. Either way, none of this belongs on the internet.

Connect the desktop viewer

The zip already holds a viewer. It is the viewer folder inside the extract folder, and the installer puts Darling Viewer shortcuts on the public desktop and in the Start menu. On the service box you need no other download.

The separate viewer installer on the same releases page is the right download for a different machine. An example is your workstation, where you do not want to extract the whole service zip. It is PerformanceMonitorDarlingViewer-darlingviewer-Setup.exe, or the Portable zip if you do not want an installer. The Setup.exe updates itself. Its install folder changes on every update, so point the DARLING_CONFIG environment variable at the exported darling.json. Do not leave files beside the exe. You can also copy the viewer folder out of the zip to the workstation and put the exported files next to the exe.

Either way, have the service box write you a ready-to-copy config folder:

.\PerformanceMonitor.Darling.Service.exe --export-viewer-config

That writes a folder with a filled-in darling.json, the store’s TLS certificate, and a README. Copy it to your workstation and the viewer connects to the store over TLS as a read-only role. The store connection verifies the certificate (VerifyFull), which is why the export includes it.

Darling desktop viewer showing Fleet Health with one healthy server, SQL2019

Same store the web dashboard reads, same read-only role, full desktop app. One difference worth knowing: the viewer lists every server in the config, so a server that has never answered shows up here as Awaiting first collection instead of being absent. The web wall shows you who has reported. The viewer also shows you who should have.

Point an AI at it

The MCP endpoint speaks Streamable HTTP and carries the same tool surface the apps use: wait stats, blocking, deadlocks, query stats, plans, configuration, the analysis engine, all served from the collected store. Wire it into Claude Code like this, with the MCP token you minted earlier:

claude mcp add --transport http darling http://192.168.1.205:5152 --header "Authorization: Bearer your-token-here"

Then ask it why the server was slow at 9am and watch it pull wait stats and blocking instead of guessing. The token gates the whole surface, and analyze_server opens live connections to your monitored servers, so treat the MCP endpoint as trusted-LAN only.

When something is down

SQL2019 was dead through this whole install, and I think the way that plays out is instructive. The preflight caught it before the monitor even existed, which is the right place to catch it. The fleet wall registers servers on first contact, so a box that has never answered does not get a card yet; the preflight output is your record of it. Once a server has reported even once, losing it flips the card to Offline in the needs-attention band and the alert engine delivers a server-unreachable alert. When someone finally starts SQL2019 back up, it registers itself on the next cycle and joins the wall with no work from me. Dead servers are a feature of production life; a monitor that only demos well against healthy fleets is a toy.

Upgrade

install-darling.ps1 registers a service. It does not lay a new build over an old one. That job belongs to upgrade-darling.ps1, which is in the same zip: it stops the service, backs up the install folder, copies the new build, confirms darling.json is unchanged and starts the service again. Each upgrade leaves a rollback backup inside the install folder. The page Upgrading Darling has the commands, screenshots, the backups and the rollback.

Uninstall

Also in the zip, run from the install folder:

.\uninstall-darling.ps1

That removes the service, the firewall rules, and the shortcuts, and deliberately leaves the store and config in place, so an uninstall is reversible by re-running the installer. If you want the collected history gone too, -PurgeData deletes it after you type the word DELETE.

PowerShell window running uninstall-darling.ps1 with PurgeData: the service is removed, then the store, credentials and logs are deleted after typing DELETE

The whole thing

Download, verify, extract, edit one config file, run one script. On my VM that was about five minutes of typing and two minutes of the service doing its first-start work, and at the end of it I had a time-series store with retention policies, a web dashboard, a desktop viewer, and an MCP endpoint watching four healthy servers and correctly complaining about a fifth. Everything opt-in, everything scoped, nothing installed on the monitored servers.

Performance Monitor is free and open source. Releases are on GitHub.