Added by theifish from SourceForge

Four new WebMethods:
---------------------------------- 

1. memory - checks memory and pagefile size

server - name of remote server
param - thresholds ([memwarning], [memcritical], [vmemwarning], [vmemcritical])
  * memwarning, memcritical - thresholds for physical memory 
  * vmemwarning, vmemcritical - thresholds for virtual memory
 you can miss any parameters you want. for example, if you miss memwarning and memcritical, the method will check only virtual memory size
  you can point either in megabytes and in percentages, for example: %50, 499, 10, %50 

2. ntevents - checks NT Events for defined period of time

server - name of remote server
param - parameters (logfiles(split by "|"),sourcenames(split by "|"),eventcodes(split by "|"),period(in minutes) ) 
- logfiles - list of LogFiles to query, for exampe: "Application|System" or just "Security"
- sourcenames - source to query, for example: Service Control Manager|eventlog
- eventcodes - event codes to query, for example: 51|7023 
- period - period in minutes for which events will be queried, for example: 10
 
you can miss any parameters, for example, if you miss logfiles than the method will check all Log Files on remote system.
method returns status depends on most important returned event, for example if there would be some event with Error type than the method will return Critical, for Warning the method return Warning. 
Common case, check for important events on Windows Server:
check_wsc!ntevents!System,Service Control Manager|NetBT|System Error|W32Time|Server|LDM|dmio|disk,,360

3. ntevent - check for special NT Event

server - name of remote server to query
param - parameters (eventtypes(splited by "|"), logfiles(splited by "|"), sourcenames(splited by "|"), eventcodes(splited by "|"),  searchstring, period(in minutes), type of returned state if found (i,w,c), type of returned state if not found (i,w,c) 
- eventtypes - list of EventTypes (integer) to query, for exampe: "1|2" or just "3".
- logfiles - list of LogFiles to query, for exampe: "Application|System" or just "Security" 
- sourcenames - source to query, for example: Service Control Manager|eventlog
- eventcodes - event codes to query, for example: 51|7023
- searchstring - string for searching in event body
- period - period in minutes to query 
- type of returned state if found - state returned if some events found with query, i - OK, w - Warning, c- Critical, default is "c"
- type of returned state if not found - state returned if no events found with query, "i"

And there you can miss any parameters.
Just for example, in my nagios I'm using this method for checking 37 event from Ntfs (User hit their quota limit):
 check_wsc!ntevent!3,System,Ntfs,37,,5,w,i 

4. process - checks a number of processes

server - name of remote server
param - warning,critical

If you miss param, the method just check for the process exist on remote system. In other cases, it check number of processes. 

Modified WebMethods:
--------------------------------
1. disks
 now you can point critical and warning in percentages
 added new parameter alloweddisks - list of disks to check, split by "|"

Example: check_wsc!disks!10%,5%,D:|E:|F:|G:
checks disks D,E,F,G; warning threshold - 10% of a disk size, critical - 5% of a disk size

2. cpu

now the method checks average load of all CPUs on remote system 
for me it was annoying when only one CPU of fours was loaded on 90%, and nagios sent me alerts.

Modified WebMethods by wolle62 (W. Wagner)
--------------------------------

1. General modifications
added a simple exception handler. this allows the new nagios_wsc.pl (>=v1.0) to display better infos
in the nagios status info.

2. uptime

Modification of calculation of uptime. Fixes a bug if server was not running using GMT.
Config-option to display normal uptime in a more simpler way (just uptime). If status is not OK it displays uptime, 
last boot and current time on server like before
      <!-- UptimeOptions
		valid values:	smart		output uptime only if status is OK
									else output last boot time & server local time as well
	-->
      <add key="UptimeOptions" value="smart" />
      
3. services

Introduced 2 new config-options: "warnmissing" now can detect missing servicenames (eg. misspelled) and issuing a warning state.
"smart" modifies the display in the status information field. if all services are running OK only a count will be displayed.
Correct running services are not displayed.

	Configuration samples (optional appsetting entries in Web.Config ):

      <!-- ServicesOptions 
		valid values:	smart		summary count of running services 
												& do not show running services in nagios status-area
						warnmissing	servicenames not found on tested server result in a warning-state
	 -->
      <add key="ServicesOptions" value="smart,warnmissing" />