VM Network IO Monitoring
Event Type: PH_DEV_MON_VM_STATE
Description: Event containing VM CPU metrics Source: All
Key Attributes:
Name | Id | Type | Description |
Event Type | eventType | string | Event type set to PH_DEV_MON_SYS_PING_STAT |
Event
Severity |
eventSeverity | uint16 | Set to 1. In general, a number between 0 (lowest severity) and 10 (highest severity) |
Event
Severity Category |
eventSeverityCat | string | Set to Low. IN general, takes the values Low, Medium and High. Event Severities 0-4 are mapped to Low, 5-8 are mapped to Medium and 9-10 are mapped to High |
Event
Receive Time |
phRecvTime | Date | Time at which AccelOps generated this event |
Reporting IP | reptDevIpAddr | Date | IP address of device reporting this event. In this case set to the device reporting the utilization (same as
Host name attribute) |
Relaying IP | relayDevIpAddr | Date | IP address of device relaying this event from the source to AccelOps. In general it could be a syslog-ng IP address but in this, since AccelOps talks to the device directly, Relaying IP is set to AccelOps IP Address. |
Raw Event
Log |
rawEventMsg | string | Raw event containing all attributes in comma separated “[Attribute] = value” format. |
vmName | |||
Host name | hostName | string | Host name (as in AccelOps CMDB) of the device whose CPU utilization is being reported |
Host IP
Address |
hostIpAddr | IP | Access IP (as in AccelOps CMDB) of the device whose CPU utilization is being reported |
phyMachName | string | ||
phyMachIpAddr | IP | ||
vSwitch | string | ||
intfName | string | ||
sentPkts | uint32 | Sent Packets | |
recvPkts | uint32 | Received Packets | |
sentBytes | uint32 | Sent Bytes | |
recvBytes | uint32 | Received Bytes | |
Poll Interval | pollIntv | uint32 | Polling interval in seconds |
Sample event:
<134>Feb 08 18:22:16 10.1.2.11 java:
[PH_DEV_MON_VM_NET_INTF_UTIL]:[eventSeverity]=PHL_INFO,[phyMachName
]=HOST-10.1.2.51,
[phyMachIpAddr]=10.1.2.51, [pollIntv]=180, [vmName]=CO159,
[morId]=vm-194, [hostName]=CO159, [hostIpAddr]=10.1.2.159,
[vSwitch]=vSwitch0, [intfName]=Network adapter 1, [sentPkts]=454,
[recvPkts]=939, [sentBytes]=102400, [recvBytes]=307200
VM Cluster CPU Utilization
VM Cluster Memory Utilization
VM Cluster Datastore I/O Utilization
VM Resource pool CPU Utilization
VM Resource pool Memory Utilization
ESX State Monitoring
ESX Datastore Utilization Monitoring
ESX Disk I/O Monitoring
<134>Oct 02 12:00:42 192.168.1.3 java:
[PH_DEV_MON_ESX_DISK_IO]:[eventSeverity]=PHL_INFO,
[hostName]=ESX3i-QA-01.prospecthills.net, [hostIpAddr]=192.168.1.3,
[pollIntv]=180, [morId]=ha-host, [diskName]=mpx.vmhba32:C0:T0:L0,
[diskReadKBytesPerSec]=9.9, [diskWriteKBytesPerSec]=0.3,
[diskReadReqPerSec]=1.215, [diskWriteReqPerSec]=0.045,
[devDiskRdLatency]=0.1, [devDiskWrLatency]=0.4, [kernDiskRdLatency]=0.0,
[totDiskRdLatency]=0.1, [totDiskWrLatency]=0.4, [kernDiskWrLatency]=0.0
ESX Datastore I/O Monitoring
Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!