Page Comparison

Table of Contents

maxLevel	2
type	flat

Introduction

The tags beginning with db.db2 identify events generated by IBM Db2 Database.

Valid tags and data tablestables

The full tag must have at least 6 six levels. The first three two are fixed asdb.db2. auditThe third level identifies the type of events sent. The fourth, fifth, and sixth levels identity the corresponding environment, application, and clone. An additional tag may be required to specify the type of the logs sent (CSV or key-value pairs)

...

Technology

...

Brand

...

Type

...

Environment

...

Application

...

Clone

...

Data type

...

db

...

db2

...

audit

...

<env>

...

<app>

...

<clon>

...

csv
kvp

.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service

Tag
Tags
Data
table
tables
IBM Db2 Database
db.db2.audit.
<env>
mcc.
<app>
server1.
<clon>
1
db.db2.audit
db.db2.audit.
<env>
mcc.server1.
<app>.<clon>.csv
1.kvp

For more information, read more about Devo tags.

Table structure

These are the fields displayed in this table:

db.db2.audit

...

db.db2.audit.<env>.<app>.<clon>.kvp

...

db.db2.audit

How is the data sent to Devo?

...

Field
Type
Extra field
Source field name
eventdate
`timestamp`
hostname
`str`
environment
`str`
venv
application
`str`
vapp
clon
`str`
vclon
timestamp
`str`
category
`str`
audit_event
`str`
event_correlator
`int4`
event_status
`int4`
userid
`str`
authid
`str`
database_name
`str`
origin_node_number
`int4`
coordinator_node_number
`int4`
application_id
`str`
application_name
`str`
object_type
`str`
access_approval_reason
`str`
access_attempted
`str`
instance_name
`str`
host_name
`str`
package_schema
`str`
package_name
`str`
package_section
`int4`
package_version
`str`
local_transaction_id
`str`
global_transaction_id
`str`
client_user_id
`str`
client_workstation_name
`str`
client_application_name
`str`
client_accounting_string
`str`
trusted_context_name
`str`
connection_trust_type
`str`
role_inherited
`str`
policy_name
`str`
policy_association_object_type
`str`
policy_association_subobject_type
`str`
policy_association_object_name
`str`
policy_association_object_schema
`str`
audit_status
`str`
checking_status
`str`
context_status
`str`
execute_status
`str`
execute_with_data
`str`
objmaint_status
`str`
secmaint_status
`str`
sysadmin_status
`str`
validate_status
`str`
error_type
`str`
data_path
`str`
archive_path
`str`
message
`str`
rawMessage
hostchain
`str`
✓
tag
`str`
✓
rawMessage
`str`
✓

Field	Type	Extra field	Source field name
eventdate	`timestamp`
hostname	`str`
environment	`str`		venv
application	`str`		vapp
clon	`str`		vclon
timestamp	`str`
category	`str`
audit_event	`str`
event_correlator	`int4`
event_status	`int4`
userid	`str`
authid	`str`
database_name	`str`
origin_node_number	`int4`
coordinator_node_number	`int4`
application_id	`str`
application_name	`str`
object_type	`str`
access_approval_reason	`str`
access_attempted	`str`
instance_name	`str`
host_name	`str`
package_schema	`str`
package_name	`str`
package_section	`int4`
package_version	`str`
local_transaction_id	`str`
global_transaction_id	`str`
client_user_id	`str`
client_workstation_name	`str`
client_application_name	`str`
client_accounting_string	`str`
trusted_context_name	`str`
connection_trust_type	`str`
role_inherited	`str`
policy_name	`str`
policy_association_object_type	`str`
policy_association_subobject_type	`str`
policy_association_object_name	`str`
policy_association_object_schema	`str`
audit_status	`str`
checking_status	`str`
context_status	`str`
execute_status	`str`
execute_with_data	`str`
objmaint_status	`str`
secmaint_status	`str`
sysadmin_status	`str`
validate_status	`str`
error_type	`str`
data_path	`str`
archive_path	`str`
message	`str`		rawMessage
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`	✓

Versions Compared

Old Version 1

New Version Current

Key

Introduction

Valid tags and data tablestables

Table structure

db.db2.audit

How is the data sent to Devo?