Windows Performance Monitoring Tools for IIS/SSO URLs
1. Failed Request Tracing
How to run: IIS Manager → Select Site → Failed Request Tracing Rules → Add Rule → Enable
Where: IIS Manager GUI
Why: Shows detailed request pipeline timing including authentication steps
What it shows: Step-by-step timing breakdown, authentication delays, handler execution time
2. IIS Request Monitor
How to run: IIS Manager → Server node → Request Monitor
Where: IIS Manager GUI
Why: Real-time view of active requests and their duration
What it shows: Current active requests, execution time, client IP, URL being processed
3. Performance Monitor (perfmon)
How to run: Start menu → perfmon → Add counters → Web Service → Average Response Time
Where: Windows Start menu or Run dialog
Why: Real-time performance counters with historical graphs
What it shows: Response times, requests/sec, connection counts over time
4. Event Viewer
How to run: Start menu → eventvwr → Windows Logs → System/Application
Where: Windows Administrative Tools
Why: Shows IIS errors, warnings, and performance events
What it shows: Error logs, authentication failures, timeout events
5. Resource Monitor
How to run: Start menu → resmon → Network tab
Where: Windows System Tools
Why: Shows network activity and connection timing in real-time
What it shows: Network connections, bandwidth usage, connection duration
6. IIS Logs
How to run: File Explorer → C:\inetpub\logs\LogFiles\W3SVC1\
Where: File system
Why: Historical record of all requests with timing data
What it shows: sc-took column shows response time in milliseconds for each request
7. Task Manager
How to run: Ctrl+Shift+Esc → Performance tab
Where: System tray or Ctrl+Shift+Esc
Why: Basic system performance overview
What it shows: CPU, memory, network usage affecting web performance
8. ETW Tracing
How to run: Command prompt → logman create trace httptrace -p Microsoft-Windows-HttpService
Where: Command prompt as administrator
Why: Low-level HTTP stack tracing
What it shows: Detailed HTTP request/response timing at kernel level
9. Netsh Trace
How to run: Command prompt → netsh trace start capture=yes provider=Microsoft-Windows-HttpService
Where: Command prompt as administrator
Why: Network packet capture with timing
What it shows: Network-level timing, SSL handshake duration, packet timing
10. WMI Queries
How to run: Command prompt → wmic process get ProcessId,WorkingSetSize
Where: Command prompt
Why: System resource usage affecting performance
What it shows: Process memory usage, CPU time, system resource consumption