Monitoring & Troubleshooting ASP.NET Applications on IIS

-

Toolbox for the IIS server

  1. net start
  2. sc query
  3. tasklist /svc
  4. netstat –ano
  5. wfetch/ wget/ curl
  6. procmon/ filemon/ regmon
  7. eventvwr
  8. mmc.exe (reliability & performance monitoring)
    1. process time & %
    2. .NET CLR
    3. ASP.NET
      1. Requests Wait Time
      2. Requests Current
      3. Requests Queued
      4. Requests Rejected

Toolbox for the browser machine

  1. ping
  2. telnet/ portcheck
  3. wfetch/ wget/ curl

When should application pools be turned into web gardens?

Web gardens can only be used if the application doesn’t use in-process session variables but rather out-of-process ones (e.g. session state service or database session state). Drivers to using web gardens are:
  1. Application makes long-running synchronous requests
  2. Application is low in availability and crashes often
  3. Application creates high CPU load on work process

Non-IIS Settings & Bottlenecks

  1. Optimum paging file size setting:
    1. 1.5x the RAM for 32-bit OS
    2. system-managed for 64-bit OS
  2. Disk queue length should always average less than 2
  3. Network utilisation should be less than 50%

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

Apache Web Server Troubleshooting

-
How to troubleshoot Apache Web Server? A few standard commands to know by hard: To confirm the modules that are or will be loaded in Apache: apachectl –M [-f <conf filename>] To check the virtual host load pattern: apachectl –S [-f <conf filename>] To test a httpd.conf file: apachectl –t [-f <conf filename>] To maintain the http server: apachectl start|stop|restart To start with a specified configuration file: apachectl –f <conf filename> Create a minimalist httpd.conf. Something like: Listen 80 ServerName myserver.com:80 ServerAdmin admin@myserver.com #ServerRoot " . " ServerRoot " /usr/local/apache2 " User nobody Group nobody #DocumentRoot " ..\wwwroot " DocumentRoot " /home/data/html " ErrorLog " logs/basic_apache.log " LogLevel debug #LoadModule log_config_module modules/mod_log_config.dll LoadModule log_config_module modules/mod_log_config.so <IfModule log_config_module> LogFormat " %h %l
Read more