zabbix監控windows相關key

標籤：following   windows   requested   physical   process   

https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/zabbix_agent/win_keys

 

proc_info[<process>,<attribute>,<type>]

 

process - process name
attribute - requested processattribute.
type - representation type(meaningful when more than one process with the same name exists)

 

The following attributes are currentlysupported:
vmsize - Size of processvirtual memory in Kbytes
wkset - Size of process workingset (amount of physical memory used by process) in Kbytes
pf - Number of page faults
ktime - Process kernel time inmilliseconds
utime - Process user time inmilliseconds
io_read_b - Number of bytesread by process during I/O operations
io_read_op - Number of readoperation performed by process
io_write_b - Number of byteswritten by process during I/O operations
io_write_op - Number of writeoperation performed by process
io_other_b - Number of bytestransferred by process during operations other than read and write operations
io_other_op - Number of I/Ooperations performed by process, other than read and write operations
gdiobj - Number of GDI objectsused by process
userobj - Number of USERobjects used by process

Valid types are:
min - minimal value among allprocesses named <process>
max - maximal value among allprocesses named <process>
avg - average value for allprocesses named <process>
sum - sum of values for allprocesses named <process>

Examples:
proc_info[iexplore.exe,wkset,sum] - to get the amount of physical memory takenby all Internet Explorer processes
proc_info[iexplore.exe,pf,avg] - to get the average number of page faults forInternet Explorer processes

Note that on a 64-bit system, a 64-bit Zabbix agent is required for this itemto work correctly.

Note: io_*, gdiobj and userobj attributes are available only on Windows 2000and later versions of Windows, not on Windows NT 4.0.

 

 

 

 

 

service_state[*]

 

0 - running
1 - paused
2 - start pending
3 - pause pending
4 - continue pending
5 - stop pending
6 - stopped
7 - unknown
255 - no such service

 

services[<type>,<state>,<exclude>]

 

type - one of all (default), automatic, manual, disabled
state - one of all (default),stopped, started, start_pending, stop_pending, running, continue_pending,pause_pending, paused
exclude - list of services toexclude it from the result.
Excluded services should be written in double quotes, separated by comma,without spaces.
This parameter is supported starting with Zabbix 1.8.1.

 

Examples:
services[,started] - list of started services
services[automatic, stopped] - list of stopped services, that should be run
services[automatic, stopped, "service1,service2,service3"] - list ofstopped services, that should be run, excluding services with names service1,service2 and service3

 

wmi.get[<namespace>,<query>]

 

namespace - WMI namespace
query - WMI query returning asingle object

 

This key is supported starting with Zabbix 2.2.0.

Examples:
wmi.get[root\cimv2,select status from Win32_DiskDrive where Name like‘%PHYSICALDRIVE0%‘] - returns the status of the first physical disk

 

 

 

 

 

 

 

eventlog[name,<regexp>,<severity>,<source>,<eventid>,<maxlines>,<mode>]

 

name - name of event log
regexp - regular expressiondescribing the required pattern
severity - regular expressiondescribing severity
The parameter accepts the following values:
“Information”, “Warning”, “Error”, “Critical”, “Verbose” (since Zabbix 2.2.0 running on Windows Vistaor newer)
In older Zabbix versions running on any Windows version it would be“Information”, “Warning”, “Error”, “Failure Audit”, “Success Audit”.
source - regular expressiondescribing source identifier (regular expression is supported since Zabbix 2.2.0)
eventid - regular expressiondescribing the event identifier(s)
maxlines - maximum number ofnew lines per second the agent will send to Zabbix server or proxy. Thisparameter overrides the value of ‘MaxLinesPerSecond‘ in zabbix_agentd.win.conf
mode - possible values:
all (default), skip (skip processing of olderdata).
The mode parameter is supportedsince Zabbix 2.0.0.

 

The item must be configured as an active check.

Examples:
eventlog[Application]
eventlog[Security,,"Failure Audit",,^(529|680)$]
eventlog[System,,"Warning|Error"]
eventlog[System,,,,^1$]
eventlog[System,,,,@TWOSHORT] - here a custom regular expression named TWOSHORT is referenced (definedas a Result is TRUE type, theexpression itself being ^1$|^70$).

“Windows Eventing 6.0” is supported since Zabbix 2.2.0.

Monitoring Windows services

This tutorial provides step-by-step instructions for setting up themonitoring of Windows services. It is assumed that Zabbix server and agent areconfigured and operational.

To monitor the up/down status of a service you need to perform thefollowing steps:

Step 1

Get the service name.

You can get that name by going to the services mmc and bringing up theproperties of the service. In the General tab you should see a field called‘Service name‘. The value that follows is the name you will use when setting upan item for monitoring.

For example, if you wanted to monitor the “workstation” service then yourservice might be: lanmanworkstation.

Step 2

Configure an item for monitoring the service, with:

• Key: service_state[lanmanworkstation]

• Type of     information: Numeric (unsigned)

• Show value: select the Windows service state value     mapping

 

本文出自 “月光疾風” 部落格，請務必保留此出處http://skykws8023.blog.51cto.com/4514277/1597389

zabbix監控windows相關key