Integration

IIS

Every request with status, latency and bytes, plus IIS and Windows Server metrics.

Category: Web servers
How data is sent: Logthread Agent
Runs on: Windows Server
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 IIS 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). No other download.
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
Log folder (optional)	Text	Default: C:\inetpub\logs\LogFiles.
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. Check IIS logging. In IIS Manager, Logging must use the W3C format (the default). Add the fields Time Taken, Bytes Sent and Host so the dashboard can show latency and traffic by site.

Step 2. Install the Logthread Agent. In PowerShell as Administrator on the IIS server: it installs the agent as a service with the IIS and Windows Server profiles. Request logs are parsed on the server; cookies are dropped.

& ([scriptblock]::Create((irm https://downloads.logthread.com/agent/install.ps1))) -Key YOUR_INGEST_KEY -Profiles windows-server,iis -Fleet

Step 3. Wait for data. IIS writes its log every minute or so; the first requests show up shortly after the next write.

Check that it works#

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

Then add#

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

Dashboard: IIS: Requests, connections, request queue, rejections, network traffic, threads and application pool state from the IIS receiver.
Dashboard: Windows Server: CPU, memory, paging, disk, network, file systems and processes from the Logthread Agent windows-server profile.
Parser: iis-w3c (Pipelines → Library)
Alert: IIS 5xx responses: service:iis status>=500, at least 20 in 10 minutes
Alert: Slow IIS requests: service:iis time_taken_ms>=5000, at least 20 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.