Audience: everyone. This page lists every page in docs/, grouped by who it is for.
Each page starts with an Audience: line under its title. The line tells you if the page is for operators, contributors or maintainers. The root README lists the main operator pages.
- Choosing an edition: Lite, Darling and Dashboard side by side.
- Lite guide: install, upgrade and configure Lite.
- Darling guides: the reading order for all Darling pages.
- Install Darling: from a downloaded zip to a service that collects data.
- Darling quick start: the short path for Windows and Linux, plus the web dashboard.
- Darling install guide (moved): a pointer from the old install guide to the new pages.
- PostgreSQL target runbook: point Darling at a PostgreSQL target, with a proof point at each step.
- Running Darling day to day: the routine tasks after the first week.
- Command line reference: every verb that the Darling service exe accepts.
- The WPF viewer: open the desktop viewer on the service host or on another machine.
- The web dashboard: turn on the browser view and reach it from another machine.
- MCP server: turn on the Darling MCP endpoint for an LLM client.
- Darling operations: the store, TimescaleDB, retention, the logs, restarts and watching the service from outside.
- Darling troubleshooting: every Darling service log line and what it means.
- Back up, restore and move the store: protect and relocate a Darling store.
- Darling store sizing: disk, RAM and vCPU for a store host.
- Clearing a Retention Held alert: steps to resume a paused retention policy.
- Backfilling the successor dailies: a runbook to backfill the interval-honest daily aggregates.
- Authentication: authentication types and credential profiles.
- Permissions: the grants that each monitored server needs.
- Platform notes: settings for AWS RDS and Aurora.
- Alerts and notifications: alert types, channels, routes and email.
- Agent dispatch: hand an alert to your own AI agent.
- Signed webhooks: check that a generic webhook post came from Darling.
- MCP server: the MCP tools, setup and client notes for both editions.
- Lite Extended Events sessions: the sessions Lite creates, and how to remove them.
- Darling and your monitored servers: what the Darling service does on each SQL Server, and the permissions it needs.
- Darling PostgreSQL targets: monitor a PostgreSQL server with Darling.
- Managed bundled PostgreSQL: the store that the Darling service runs for itself.
- Darling configuration reference: where each
darling.jsonsetting lives,postgres,servers,peers,heartbeatandreads. - Darling alert and notification settings: the
alerts,analysis,smtpandwebhooksblocks, and the notification routes. - Darling agents and alert sources: hand an alert to your own agent, practice requests, and logins for systems that send alerts.
- Darling MCP configuration: the
mcpblock ofdarling.json. - Darling web dashboard configuration: the
webblock ofdarling.json. - Darling collector schedules and switches: the verbs and tools that turn a collector on or off and set when it runs.
- Darling security and agent changes: the store's schemas and roles, the agent change list, and Level 2.
- Darling network endpoints: reach the store, MCP and the web dashboard over the LAN.
- Features and screenshots: what you get, with screenshots.
- Tabs: what each tab in Lite and the Darling viewer shows.
- Agent job monitoring: running SQL Agent jobs and jobs that run too long.
- Performance impact: the load on monitored servers and on the local host.
- Troubleshooting: common problems for Lite and Darling.
- How collection works: a tour of the collection pipeline.
- Support and sponsorship: commercial support and sponsorship.
- Third-party components: components that ship with the product, and their licenses.
- Changelog files: the release notes for each version, one file per version.
These pages are kept as history. They record the reasoning at the time. Do not follow them as procedures.
- PostgreSQL alerting scoping note: why the PostgreSQL alert thresholds are constants.
- PostgreSQL blocking chains design note: how PostgreSQL blocking collection was designed and what building it changed.
- Building from source: folder structure and build commands.
- Release upgrade validation: how to test an upgrade from a released build.