app.cisco
Introduction
The tags beginning with app.cisco
identify events generated by Cisco applications.
Valid tags and data tablesÂ
The full tag must have 4 levels. The first two are fixed as app.cisco
. 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 |
---|---|---|
Cisco Unified Communications Manager |
|
|
For more information, read more About Devo tags.
Table structure
These are the fields displayed in this table:
Field | Type | Field transformation | Source field name | Extra fields |
---|---|---|---|---|
eventdate |
| Â | Â | Â |
hostname |
| Â | Â | Â |
internal_id |
| Â | Â | Â |
timestamp |
| parsedate(timestamp_string, dateformat("MMM DD YYYY HH:mm:ss.SSS [UTC]", "UTC", "en-US")) | timestamp_string | Â |
event |
| Â | Â | Â |
user_id |
| Â | Â | Â |
client_address |
| Â | Â | Â |
severity |
| Â | Â | Â |
event_type |
| Â | Â | Â |
resource_accessed |
| Â | Â | Â |
event_status |
| Â | Â | Â |
compulsory_event |
| Â | Â | Â |
audit_category |
| Â | Â | Â |
component_id |
| Â | Â | Â |
correlation_id |
| Â | Â | Â |
audit_details |
| Â | Â | Â |
app_id |
| Â | Â | Â |
cluster_id |
| Â | Â | Â |
node_id |
| Â | Â | Â |
description |
| Â | Â | Â |
hostchain |
|  |  | ✓ |
tag |
|  |  | ✓ |
rawMessage |
|  |  | ✓ |
Â