db.postgresql

[ 1 Introduction ] [ 2 Valid tags and data tables ] [ 3 Table structure ]

Introduction

The tags beginning with db.postgresql identify events generated by PostgreSQL.

Valid tags and data tables

The full tag must have at least three levels. The first two are fixed as db.posygresql. The third level identifies the type of events sent. The fourth, fifth, and sixth levels identity the corresponding environment, application, and clone.

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

Product / Service	Tags	Data tables

Product / Service	Tags	Data tables
PostgreSQL	`db.postgresql.audit.venv.vapp.vclone`	`db.postgresql.audit`
PostgreSQL	`db.postgresql.out.venv.vapp.vclon`	`db.postgresql.out`

For more information, read more about Devo tags.

Table structure

These are the fields displayed in these tables:

db.postgresql.audit

Field	Type	Source field name	Extra fields

Field	Type	Source field name	Extra fields
eventdate	`timestamp`
hostname	`str`
environment	`str`	venv
application	`str`	vapp
clone	`str`	vclone
log_time	`timestamp`
user_name	`str`
database_name	`str`
process_id	`int4`
connection_from	`str`
session_id	`str`
session_line_num	`int8`
process_status	`str`
session_start_time	`timestamp`
virtual_transaction_id	`str`
transaction_id	`int8`
error_severity	`str`
sql_state_code	`str`
message	`str`
detail	`str`
hint	`str`
internal_query	`str`
internal_query_pos	`int4`
context	`str`
query	`str`
query_pos	`int4`
location	`str`
application_name	`str`
backend_type	`str`
command_tag	`str`
audit_tag	`str`
type	`str`
hostchain	`str`		✓
tag	`str`		✓
rawMessage	`str`		✓

db.postgresql.out

Field	Type	Field transformation	Source field name	Extra fields

Field	Type	Field transformation	Source field name	Extra fields
eventdate	`timestamp`
machine	`str`
environment	`str`		venv
application	`str`		vapp
clon	`str`		vclon
log_prefix	`str`	`join(log_prefix_, ' ')`	log_prefix_
log_level	`str`
message	`str`
rawMessage	`str`		rawSource	✓
hostchain	`str`			✓
tag	`str`			✓