Availability Monitoring Events
Availability Monitoring Events
AccelOps generates the following events related to availability monitoring
Ping Stat Monitoring
Synthetic Monitoring Success Synthetic Monitoring Failure
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. |
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 |
Avg Round
Trip Time |
avgDurationMSec | uint32 | Average Round trip time from the ping tests done during this interval |
Max Round
Trip Time |
maxDurationMSec | uint32 | Max Round trip time from the ping tests done during this interval |
Min Round
Trip Time |
minDurationMSec | uint32 | Min Round trip time from the ping tests done during this interval |
Packet Loss
Pct |
pktLossPct | double | Packet loss percentage from the ping tests done during this interval |
System
Down Time |
sysDownTime | uint32 | Amount of time during this polling interval that there was 100% ping loss |
System
Degraded Time |
sysDegradedTime | uint32 | Amount of time during this polling interval that there was 50%+ ping loss |
Poll Interval | pollIntv | uint32 | Polling interval in seconds |
Synthetic Transaction Monitoring Success
Event Type: PH_DEV_MON_EUM_SUCCESS
Description: Successful Synthetic transaction monitoring test Source: All Key Attributes:
Name | Id | Type | Description |
Event Type | eventType | string | Event type set to PH_DEV_MON_SYS_EUM_SUCCESS |
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. |
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 |
Synthetic
Transaction Monitor Name |
endUserMonitorName | string | Name of the Synthetic Transaction Monitor |
Synthetic
Transaction Monitor Step |
endUserMonitorStep | string | Particular step of the Synthetic Transaction Monitor, in case the transaction monitor involves multiple steps. |
Application
Protocol |
appTransportProto | string | Application protocol such as HTTP |
Application Port | appPort | string | Port number such as 443 |
Application
Response Time |
appResponseTimeMSec | uint32 | Synthetic transaction response time (ms) |
Poll Interval | pollIntv | uint32 | Polling interval in seconds |
Synthetic Transaction Monitoring Failure
Event Type: PH_DEV_MON_EUM_FAIL
Description: Failed Synthetic transaction monitoring test Source: All Key Attributes:
Name | Id | Type | Description |
Event Type | eventType | string | Event type set to PH_DEV_MON_SYS_EUM_SUCCESS |
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. |
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 |
Synthetic
Transaction Monitor Name |
endUserMonitorName | string | Name of the Synthetic Transaction Monitor test |
Synthetic
Transaction Monitor Step |
endUserMonitorStep | string | Particular step of the Synthetic Transaction Monitor, in case the transaction monitor involves multiple steps. |
Application
Protocol |
appTransportProto | string | Application protocol such as HTTP |
Application Port | appPort | string | Port number such as 443 |
Reason for Error | errReason | uint32 | Reason for failed Synthetic Transaction Monitor test |
Poll Interval | pollIntv | uint32 | Polling interval in seconds |
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!