Integration

Microsoft SQL Server

Performance metrics, the slowest statements with waits and blocking, and the ERRORLOG.

Category: Databases
How data is sent: Logthread Agent
Runs on: Windows Server, Linux
Status: Beta

How it works#

Answer a few questions. They only fill in the setup steps. Nothing on this page connects to your servers: Logthread never reaches into your network.
Run one command on the Microsoft SQL Server machine. The next page shows the command with this connector's ingest key filled in. It downloads the Logthread Agent from downloads.logthread.com and installs it as a service (Windows Server, in PowerShell as Administrator or Linux, as root with sudo). No other download. If the agent cannot run on that machine, run it on one that can reach Microsoft SQL Server over your private network and set the server below.
Data arrives. Everything is collected inside your environment. It is sent over outbound HTTPS (port 443) to ingest.logthread.com. Nothing is opened to the internet: no inbound ports, VPN or public access to your servers. The connection page shows what has arrived and turns Active with the first record.

What you answer#

Question	Answer	Notes
Operating system	`windows` (Windows Server), `linux` (Linux)	Default: `windows`.
Sign in as	`windows` (The agent service (Windows authentication)), `sql` (A SQL login)	Windows authentication needs no password. On Linux a SQL login is used. Default: `windows`.
SQL Server host	Text	Default: the host the agent runs on.
Port	Text	Default: 1433.
Labels (optional)	Text	For Fleet and filtering, for example env=prod.
Manage this agent from Fleet	Yes or no	Change its configuration from Logthread later without logging in to the host. Default: `Yes`.

Setup#

These are the steps for the default answers. In the app, they follow your answers, and the connector's ingest key replaces YOUR_INGEST_KEY.

Step 1. Create a read-only monitoring login. Only what the agent needs to read performance data: no write access and no table data. Statement text is masked on the host before it is sent.

In SQL Server Management Studio or sqlcmd:

-- The agent service runs as LocalSystem. On the SQL Server host it signs in as
-- NT AUTHORITY\SYSTEM; from another host, use its computer account DOMAIN\HOST$.
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS;  -- skip if it exists
GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM];
GRANT VIEW ANY DEFINITION TO [NT AUTHORITY\SYSTEM];
GRANT VIEW ANY DATABASE TO [NT AUTHORITY\SYSTEM];

Step 2. Install the Logthread Agent. In PowerShell as Administrator on the SQL Server host: it installs the agent as a service with the SQL Server profile, using this connection's own ingest key.

& ([scriptblock]::Create((irm https://downloads.logthread.com/agent/install.ps1))) -Key YOUR_INGEST_KEY -Profiles windows-server,sqlserver -SqlServerDsn 'server=.;port=1433;Integrated Security=SSPI;encrypt=true;TrustServerCertificate=true' -Fleet

Step 3. Wait for data. Metrics arrive within a minute; the slowest statements and ERRORLOG lines follow as they happen.

Check that it works#

The connection page under Integrations counts what has arrived and turns Active with the first record. In Explore, search service:sqlserver.

Then add#

Each is one click on the connection page and opens with your data, so you can check it before saving.

Dashboard: SQL Server: Batch requests, compilations, page life expectancy, buffer cache, locks, deadlocks, connections and transaction log from the SQL Server receiver.
Alert: SQL Server errors: service:sqlserver severity:(error|fatal), at least 5 in 10 minutes
Alert: SQL Server failed logins: service:sqlserver "Login failed", at least 10 in 10 minutes

Set it up under Integrations in the app, or from an AI agent with MCP (add_integration). All integrations: Integrations guide. Next: find what it sends in Explore and live tail.