FortiSIEM Application Monitoring Events

Event Type: PH_DEV_MON_TOMCAT_CPU

Description: Event containing Tomcat Application Server CPU utilization Source: Tomcat (JMX) Sample Event:

<134>Jan 22 01:57:32 10.1.2.16 java:

[PH_DEV_MON_TOMCAT_CPU]:[eventSeverity]=PHL_INFO,[destIpAddr]=10.1.2.16,[hostIpAddr]=10.1.2.16,[hostName]=SH-WIN08R2JMX,[destDevPort]=9218,[appVersion]=Apache Tomcat/7.0.27,[appServerState]=STARTED,[sysUpTime]=2458304,[cpuUtil]=0  Key Attributes:

Name Id Type Description
Event Type eventType string Event type set to PH_DEV_MON_TOMCAT_CPU_MET
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 IP 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 IP 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
x destDevPort uint32 x
x appVersion uint32 x
x appServerState double x
System

Uptime

sysUpTime uint64 Tomcat Uptime
CPU

Utilization

cpuUtil double CPU utilization of Apache processes

Event Type: PH_DEV_MON_TOMCAT_MEMORY

Description: Event containing Tomcat Application Server memory utilization Source: Tomcat (JMX) Sample Event:

<134>Jan 22 01:57:32 10.1.2.16 java:

[PH_DEV_MON_TOMCAT_MEMORY]:[eventSeverity]=PHL_INFO,[destIpAddr]=10.1.2.16,[hostIpAddr]=10.1.2.16,[hostName]=SH-WIN 08R2-JMX,[destDevPort]=9218,[appVersion]=Apache

Tomcat/7.0.27,[appServerState]=STARTED,[freeMemKB]=116504,[freeSwapMemKB]=2974020,[memTotalMB]=4095,[swapMemTotalM

B]=8189,[virtMemCommitKB]=169900,[memUtil]=98,[swapMemUtil]=65,[heapUsedKB]=18099,[heapMaxKB]=932096,[heapCommitKB]= 48896,[heapUtil]=37,[nonHeapUsedKB]=22320,[nonHeapMaxKB]=133120,[nonHeapCommitKB]=24512,[nonHeapUtil]=91  Key Attributes:

 

 

Name Id Type Description
Event Type eventType string Event type set to PH_DEV_MON_TOMCAT_CPU_MET
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 IP 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 IP 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
System

Uptime

destDevPort uint64 Tomcat Uptime
CPU

Utilization

appVersion double CPU utilization of Apache processes
appServerState
freeMemKB
freeSwapMemKB
memTotalMB
swapMemTotalMB
virtMemCommitKB
memUtil
swapMemUtil
heapUsedKB
heapMaxKB
heapCommitKB
heapUtil
nonHeapUsedKB
nonHeapMaxKB
nonHeapCommitKB
nonHeapUtil

Having trouble configuring your Fortinet hardware or have some questions you need answered? Ask your questions in the comments below!!! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!

Leave a Reply

Name *
Email *
Website