Using Mysql Tables; Mysql Incident Table - Symantec 10521146 - Network Security 7120 Administration Manual

332 SQL reference

Using MySQL tables

Using MySQL tables

MySQL incident table

Table B-3 MySQL Incident Table
Field Name Type
class varchar(33)
clusterID integer
crtTime integer
custID varchar(41)
devid varchar(33)
devName varchar(41)
eventNum integer
family varchar(33)
flowcookie text
This section describes the structure of the incident and event tables that
Symantec Network Security uses to export data to a MySQL database.
To configure software or appliance nodes to export tables to MySQL, see also
"Exporting to SQL" on page 257.
Note: MySQL supports
255. Therefore,
varchar
become fields, but if smaller than 255, they remain
text
MySQL incident table
■
MySQL event table
■
The following table describes the structure of the table that Symantec Network
Security uses to export incident data to a MySQL database:
Description
Indicates the class of the best event.
Indicates the Network Security cluster ID where
the incident originated
Indicates the time that this incident was created. Standard UNIX time format
Indicates the Customer ID of the best event.
Indicates the ID of the device (deviceID from
topology table) where the best event was
detected.
Indicates the device name of the best event.
Indicates the eventNum of the best event. This
is the event that best represents this incident
(usually the one with the highest severity).
Indicates the family of the best event.
Indicates the flowcookie of the best event.
, but the maximum size of that field is limited to
varchar
fields that are larger than 255 in the MySQL statements
.
varchar
Notes
Used internally