Check the reference vendor documentation here.
Introduction
The tags beginning with network.hp identify events generated by HP.
Valid tags and data tables
The full tag must have at least 3 levels. The first two are fixed as network.hp. The third level identifies the type of events sent. The fourth level indicates the event subtype.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
|---|---|---|
HP printers |
|
|
HP networking switches |
|
|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
For more information, read more About Devo tags.
How is the data sent to Devo?
For network.hp.* tags, define the following relay rule to send these events to Devo:
Source message -
^\d+\s([\w\-\.]+?):Target tag -
network.hp.switch.\m1Check both the Stop processing and Sent without Syslog tag options.
Note that in the Target tag, m1 should be the system_module (group capture 1) in the Source message RegEx.
Table structure
These are the fields displayed in these tables: