IIS Tracer web site monitoring tool

ActiveX/VBSScript registry editor  ActiveX NT User account manager  Export MDB/DBF from ASP
Url replacer, IIS url rewrite Active LogFile  Email export  ActiveX/ASP Scripting Dictionary object
 IISTracer, real-time IIS monitor
 Huge ASP upload - upload files with progress.
IIS ISAPI filter
 License and ordering info >>
 Version history >>
 Configuration of IIS Tracer web site monitoring tool >>
 Interesting captures (CodeRed attack) with IIS Tracer web site monitoring tool >>
 Frequetly Asked Questions >>
 Description   
         IISTracer is a real-time internet web site monitoring tool for Microsoft IIS (all versions). The software lets you show what is happenning on IIS server right now. You can see or log state of each request, incomming/outgoing bytes, http headers and several request running times.
      IISTracer shows a state of running scripts (.asp, .aspx, asp.net, .cfm, .php, .cgi, ...), applications (.dll, .exe, ..) and a big downloads (.mp3, .zip, ...).
      It lets you also monitor what script or which client (IP) hangs-up your server.
       New  - You can stop long running requests (uploads/downloads).
 Reviews   
        Keep an Eye on Your Web Site in Real Time
      Souping Up Your IIS Server
      
 Links   
        
      Download latest version, v 2.8.0  
      The version works with all IIS versions from IIS1 to IIS6 (7). It is fully functional time-limitted demo (60 days). See IIS6 notes and Version history.
      
      Download 2.50 version (IIS 1-5)
      The version does not work with IIS6 (7). See version history.
      
      IIS Tracer web site monitoring tool home page.
      Download this help.
 Features   
 
 New - stop of long running request function 

IIS state logging

Configuration

  • User friendly configuration application to install IISTracer to local/remote IIS
  • Works with all versions of IIS (from IIS1 to IIS6)

Monitoring functions and values

  • Real-time monitoring of running ISAPI scripts (.asp, .cgi, .idc, .idq ...) 
  • Real-time monitoring of big downloads
  • Info about last long-running scripts
Values and views
  • Current number of running requests (scripts/downloads)
  • Current state of the request
  • Script start time and running time with precision up to milisecond.
  • Request and response content-length.
  • Current script incomming and outgoing bytes.
  • Complette URL, method, http header data and Client IP address.
  • Mixed/separated view of active/completted requests ordered by time

Interface and configuration

      To monitor web-site uptime and response times and get a notification when your site is on problems or down please see WebChecker - up-time web site monitoring and problem notification.
 Sample views of IISTracer interface   
  Sample 1: upload a file, some image downloads.
 Select view:  Active  Active/Completed  All  Sort order:  Descending  Other: 
 Configuration  About  Full version. 
 Actual state:  Time: 12:58:17.411  Active requests: 5  Completed Requests: 25  All Requests: 30 
X Start 
 Time 
 Running 
 [ms] 
 State  Client  In raw 
 [B] 
 In Content 
 length [B] 
 Out raw
 [B] 
 Out Content 
 length [B] 
 URL 
X 12:58:09.528 7 883  Send data  194.228.134.112 ns 65 763 68 783  GET http://tady.cz/annak/images/gal4/girardin14.jpg
X 12:58:11.418 5 992  Send data  194.228.134.112 ns 24 803 51 188  GET http://tady.cz/annak/images/gal4/girardin11.jpg
X 12:58:14.624 2 786  Read data  217.11.235.133 17 520 51 391 89 ns  POST http://www.multiweb.cz/e/default.asp?UploadID=11&Action=UP
X 12:58:15.268 2 143  Send data  212.47.11.83 ns 24 804 84 201  GET http://www.hok.cz/praha_povoden9/voda023.jpg
X 12:58:15.514 1 896  Send data  194.25.40.4 ns 49 380 84 201  GET http://www.hok.cz/praha_povoden9/voda023.jpg


Sample 2: Typical problematic long-running script (.asp)
X Start 
 Time 
 Resp. 
 Time 
 Running 
 [ms] 
 State  Client  In raw 
 [B] 
 In Content 
 length [B] 
 Out raw
 [B] 
 Out Content 
 length [B] 
 URL 
X 8:20:16.532 213 189 271  Send data  198.141.197.3 ns 34 499 un  GET http://www.fin.cz/katalog/financni.asp?A=D&IDS=17&S=13810
X 8:23:18.603 7 200  Send data  160.218.40.131 ns 24 804 un  GET http://r.kde.cz/NEWS/autoimg/5/2939.jpg
X 8:23:20.534 163 5 269  Send data  152.66.10.60 ns 57 947 un  GET http://www.fin.cz/nazory/defaultpg_T768_PR57029.htm
X 8:23:24.712 1 091  Send data  80.188.201.158 ns 40 175 un  GET http://x.kde.cz/new/css/alia.css

      The script http://www.fin.cz/katalog/financni.asp is a typical problematic script, which may your server rapidly slow down. The script already sent all data to a client (Out raw data are 34499B and the number do not grow), but it is still working. Running time of the script is more than 3 minutes. The script probably contains some endless do-loop, but the do-loop is placed at the end of code, after client receives all required data. Or there may be some problematic code working with database at the end of script (some cross-locking SQL commands). The script ends after Server.ScriptTimeout.

      You cannot see a problem as a client - everything looks well from client side and your clients do not report problem. But you can usually see the problem at server-side.

      You can see that other scripts are rapidly slow-down. You can see that CPU Usage is at 100% at the time, if you monitor your server using performance monitor or other tool (task manager). The problematic process is usually dllhost.exe (.asp), aspnet_wp.exe (.aspx asp.net pages) or inetinfo.exe (if you run scripts in Low/IIS process application protection or in older versions of IIS). IISTracer is exactly designed to reveal such kind of problematic scripts. See also Monitor extremly slow or problematic scripts (ASP hangs, not responding web)



Sample 3: Scripts processing POST data
X Start 
 Time 
 Resp. 
 Time 
 Running 
 [ms] 
 State  Client  In raw 
 [B] 
 In Content 
 length [B] 
 Out raw
 [B] 
 Out Content 
 length [B] 
 URL 
X 9:03:10.756 65 154  Read data  194.228.94.242 560 560 89 un  POST http://www.fin.cz/nazory/default.asp
X 9:04:08.533 40 7 378  Send data  195.39.45.138 ns 66 926 un  GET http://www.fin.cz/kurzy/kurzy.asp?A=ON
X 9:04:13.435 2 476  Read data  212.71.153.100 5 412 5 410 89 un  POST http://www.zpravodaj.cz/m.asp
X 9:04:15.062 849  Preproc headers  212.71.128.66 ns un  GET http://diskuze.fin.cz/nazory/defaultpg_T80_PR125562.htm
X 9:04:15.155 755  Preproc headers  62.168.13.202 ns un  GET http://oh2004.zpravodaj.cz/
X 9:04:15.820 91  Preproc headers  195.70.148.66 ns un  GET http://kurzy.fin.cz/kurzy/kurzy.asp?A=P&M=SKK

      The scripts http://www.fin.cz/nazory/default.asp and http://www.zpravodaj.cz/m.asp received all POST data, [In raw] = [In Content length], but they still did not send a response to a client. Client for '/nazory/default.asp' cannot see response for more than one minute.

      This situation is usually not so critical, but the script /nazory/default.asp is strong adept for time/performance optimization.



Sample 4: Another long-running ASP requests (cat.dat, default.asp)
 Select view:  Active  Active/Completed  All  Sort order:  Descending  Other: 
 Configuration  About  Full version. 
 Actual state:  Time: 13:01:17.813  Active requests: 13  Completed Requests: 25  All Requests: 38 
X Start 
 Time 
 Running 
 [ms] 
 State  Client  In raw 
 [B] 
 In Content 
 length [B] 
 Out raw
 [B] 
 Out Content 
 length [B] 
 URL 
X 13:00:56.715 21 098  Preproc headers  194.108.51.155 ns un  GET http://www.multiweb.cz/e/cat.dat?h=1
X 13:00:56.898 20 915  Authentication  194.108.51.155 ns un  GET http://www.multiweb.cz/e/default.asp?lv=2&Action=NF
X 13:01:11.567 6 246  Preproc headers  62.168.18.1 ns un  GET http://www.multiweb.cz/e/cat.dat?h=1
X 13:01:12.191 5 622  Send data  212.90.230.87 ns 24 804 48 642  GET http://www.multiweb.cz/passat/nejhezci.jpg
X 13:01:13.621 4 192  Preproc headers  147.32.80.9 ns un  GET http://www.multiweb.cz/e/cat.dat?h=1
X 13:01:13.644 4 169  Authentication  147.32.80.9 ns un  GET http://www.multiweb.cz/e/default.asp?Action=PNF
X 13:01:14.696 3 117  Send data  212.90.230.87 ns 16 612 64 125  GET http://www.multiweb.cz/passat/decentlimuzine.jpg
X 13:01:15.953 1 859  Preproc headers  62.24.91.239 ns un  GET http://www.multiweb.cz/e/cat.dat?h=1
X 13:01:15.987 1 826  Authentication  62.24.91.239 ns un  GET http://www.multiweb.cz/e/default.asp?Action=PNF
X 13:01:16.070 1 743  Preproc headers  62.168.18.190 ns un  GET http://www.multiweb.cz/e/cat.dat?h=1
X 13:01:16.318 1 495  Authentication  62.168.18.190 ns un  GET http://www.multiweb.cz/e/default.asp?lv=2&Action=NF
X 13:01:16.787 1 025  Authentication  193.86.241.130 227 un  PROPFIND http://www.multiweb.cz/citrusy/obecne.rtf
X 13:01:16.884 929  Authentication  217.11.235.67 ns un  GET http://www.multiweb.cz/e/u.dat?o
 Instalation   
        IIS Tracer ISAPI filter is loaded. You can try /iistracer http interface on your IIS server.1. Download and install IISTracer DLL
      2. Run Configuration application - basic setup and install filter to IIS to add IISTracer as IIS filter DLL (or see instructions on Configuration application - basic setup and install filter to IIS page).
      3. Restart W3SVC service to load IISTracer to IIS
      4. See what people are doing on your website RIGHT NOW using IISTracer http interface! You can find the interface on http://yourserver/iistracer
      5. Be sure you have changed /iistracer script to your custom value to hide IISTracer http interface to other users. See Protect http interface using Username/Password, Client IP and certificates

© 1996 – 2007 Antonin Foller, Motobit Software, help@pstruh.cz