| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
The tags beginning with ap.cisco identify events generated by access point devices belonging to Cisco.
Valid tags and data tables
The full tag must have 3 levels. The first two are fixed asap.cisco. The third level identifies the type of events sent.
Product / Service
Data tables
Cisco Wireless LAN Controller
ap.cisco.wlc
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data |
|---|
tables | ||
|---|---|---|
Cisco Wireless LAN Controller |
|
|
For more information, read more about Devo tags.
How is the data sent to Devo?
Logs generated by Cisco must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rule below:
Source port - Any available port
Target tag -
ap.cisco.wlcSent without syslog tag - ✓
No 3rd-party mechanism is used. No collector is needed.
Table structure
These are the fields displayed in this table:
ap.cisco.wlc
Field | Type | Source field name | Extra fields |
|---|---|---|---|
eventdate |
|
|
stringmachine |
|
vmachine |
stringlevel |
|
stringvlevel |
syslogFacility |
string
|
embFacility | |
apName |
string
|
| |
task |
string
|
| |
serverdate |
|
string
| |
facility |
string
|
| ||
priority |
|
| |
mnemonic |
string
|
| |
message |
string
rawSource
string
|
| ||
rawMessage |
|
| ✓ |
hostchain |
|
| ✓ |
tag |
|
| ✓ |