sdn.aviatrix
Introduction
The tags beginning with sdn.aviatrix
identify events generated by Aviatrix.
Valid tags and data tables
The full tag must have at least 3 levels. The first two are fixed as sdn.aviatrix
. The third level identifies the type of events sent, and 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 |
---|---|---|
Aviatrix |
|
|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
How is the data sent to Devo?
Logs generated by Aviatrix must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rule below:
Relay rule 1
This rule applies to the following parsers:
sdn.aviatrix.controller.gwsysstats
sdn.aviatrix.controller.gwnetstats
sdn.aviatrix.controller.tunnel
sdn.aviatrix.controller.gateway
sdn.aviatrix.controller.cmd
Source port - Customer source port, for example
13007
Source data -
Aviatrix(Gateway|Tunnel|CMD|Gw\w+)
Target tag -
sdn.aviatrix.controller.\\d1
Target message -
\\d0
Stop processing - ✓
Relay rule 2
This rule applies to the following parsers:
sdn.aviatrix.controller.auth
Source port - Customer source port, for example
13007
Source data -
^(auth.log)
Target tag -
sdn.aviatrix.controller.auth
Target message -
\\d0
Stop processing - ✓
Relay rule 3
This rule applies to the following parsers:
sdn.aviatrix.controller.syslog
Source port - Customer source port, for example
13007
Source data -
^(syslog)
Target tag -
sdn.aviatrix.controller.syslog
Target message -
\\d0
Stop processing - ✓
If none of the previous regex matches the event, then the event will be sent to sdn.aviatrix.controller.unknown
Table structure
These are the fields displayed in these tables: