Darling documentation

This page describes Darling v3.13.0. The source of this page is on GitHub at that version.

Audience: operators.

Read these pages in this order. After the install, each page is complete on its own.

  1. Install Darling: from a downloaded zip to a service that collects data.
  2. The WPF viewer: the desktop app, on the service host or on another machine.
  3. The web dashboard: the browser view that the service serves.
  4. MCP server: the endpoint for an LLM client.
  5. Running Darling day to day: add or remove a server, change a password, rotate a token, pause, upgrade, uninstall, and where everything is.
  6. Command line reference: every verb of the service exe, with exit codes.
  7. Darling and your monitored servers: what the service does on each SQL Server, its Extended Events sessions, and the permissions it needs.
  8. PostgreSQL Targets: monitor a PostgreSQL server.
  9. Managed Bundled PostgreSQL: the store that the service runs for itself.
  10. Configuration Reference: where each setting lives, postgres, servers, peers, heartbeat and reads.
  11. Alert and notification settings: the alerts, analysis, smtp and webhooks blocks, and the notification routes.
    • The Slack bot: the one Slack app and its manifest, the bot and app-level tokens, the per-store bot channel, and the Socket Mode listener.
  12. Agents and alert sources: hand an alert to your own agent, practice requests, and logins for systems that send alerts.
  13. MCP configuration: the mcp block.
  14. MCP tools and their store tables: every MCP tool and the store tables that it reads or changes.
  15. Web dashboard configuration: the web block.
  16. Collector schedules and switches: why there are no schedule settings, and the verbs and tools that change a collector.
  17. Operations: the store, TimescaleDB, retention, the logs, restarts and watching the service from outside.
  18. Security and agent changes: the store’s schemas and roles, the agent change list and its undo, and Level 2.
  19. Opt-in Network Endpoints (LAN): reach the store, MCP and the web dashboard from another machine.
  20. Troubleshooting: a table of what you see, the likely cause and the fix, for Darling and Lite.
  21. Darling troubleshooting: every service log line and what it means.
  22. The front door: one MCP address and one web address in front of several stores.
  23. Run Darling on Kubernetes: the Helm chart in this repository, with its two store modes, probes and upgrade steps.

The Darling operator guide is now a short index. Its old headings link to these pages.

Every page and its sections