Data collection
Microsoft IIS
Microsoft IIS W3C extended access logs parsed into HTTP request fields with response-status severity. Directive lines pass through untouched.
- Logs
- Collector-based
- Package 1.0.1
What it collects
- Signals
- Logs
- How it collects
- Log file tailing (
filelog) - Where it runs
- On a Tracix Collector you install. Agentless collection is not offered for it.
- Package version
- 1.0.1
Included in the package
- IIS overview dashboard, 7 panels
- A log-parsing pipeline that maps fields to OpenTelemetry semantic conventions first
How to connect it
- 01Open the connect wizardIn the Tracix console, open Integrations and pick Microsoft IIS.
- 02Install the Tracix CollectorInstall it where it can reach the data, then add the integration to that collector's policy.
- 03Fill in the connectionEnter the settings the wizard asks for. Collectors pick up the policy change on their own.
More in web servers
All packages in web servers
NGINX
Web servers
Active connections, request rate, response statuses from /nginx_status.
Metrics
HAProxy
Web servers
Backend health, queue depth, request rate, response codes via the stats socket.
Metrics
Apache HTTPD
Web servers
Worker pool, request rate, byte rate from the Apache mod_status endpoint.
Metrics
Apache Tomcat
Web servers
Request and error rates, traffic, processing time, connector thread pool saturation, and JVM heap via Jolokia.
Metrics
Oracle WebLogic
Web servers
Running versus configured server counts, per-server open sockets and state, and deployed application count from the WebLogic RESTful Management API.
Metrics
PHP-FPM
Web servers
Pool process saturation, listen queue depth, accepted connection rate, and slow request counts from the PHP-FPM status page.
Metrics
Connect Microsoft IIS to Tracix
Start free and connect it from the console, or book a demo and we will walk through your environment with you.