db.netezza
Introduction
The tags beginning with db.netezza identify events generated by Netezza Performance Server.
Valid tags and data tables
The full tag must have 6 levels. The first two are fixed as db.netezza. The third, fourth, and fifth levels are variable and identify the corresponding environment, application, and clon. The sixth level is always fixed as out.
Technology | Brand | Type | Subtype 1 | Subtype 2 | Subtype 3 |
---|---|---|---|---|---|
db | netezza |
|
|
|
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
db.netezza.<env>.<app>.<clon>.out | db.netezza.out |
How is the data sent to Devo?
Logs generated by Netezza Performance Server are forwarded to Devo using a dedicated collector. Contact us if you need to forward these events to your Devo domain so we can guide you through the process.
Log samples
The following are sample logs sent to each of the db.netezza data tables. Also, find how the information will be parsed in your data table under each sample log.
Extra columns
Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns.
db.netezza.out
2012-09-11 21:39:38.476 localhost=127.0.0.1 db.netezza.dev.agent.1.out: 2020-10-30 15:43:18.463591 EDT [30962] DEBUG: Session id is 3707179 2012-09-11 21:39:38.476 localhost=127.0.0.1 db.netezza.dev.agent.1.out: 2020-10-30 15:43:18.466911 EDT [30962] DEBUG: QUERY: set datestyle to 'ISO'; 2012-09-11 21:39:38.476 localhost=127.0.0.1 db.netezza.dev.agent.1.out: 2020-10-30 15:43:18.486271 EDT [30962] DEBUG: QUERY: SET CLIENT_WORKSTATION_NAME TO ''
And this is how the log would be parsed:
Field | Value | Type | Extra field |
---|---|---|---|
hostchain |
|
| ✓ |
tag |
|
| ✓ |
environment |
|
| |
application |
|
| |
clon |
|
| |
message |
|
|