| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
The tags beginning with db.netezza identify events generated by belonging to Netezza Performance Server.
Valid tags and data tablestables
The full tag must have 6 at least three levels. The first two are fixed asdb.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
...
<env>
...
<app>
...
<clon>
...
out
level identifies the type of events sent.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service |
|---|
Tags | Data |
|---|
tables | |
|---|---|
Netezza Performance Server |
|
|
|
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.For more information, read more about Devo tags.
Table structure
These are the fields displayed in this table:
Field | Type | Extra field | Source field name |
|---|---|---|---|
eventdate |
| ||
environment |
| venv | |
application |
| vapp | |
clon |
| vclon | |
rawMessage |
| ✓ | rawSource |
message |
| ||
hostchain |
| ✓ | |
tag |
| ✓ |