| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
The tags beginning with cloud.meraki identify events generated by Cisco Meraki.
Valid tags and data tables
The full tag must have 4 levels. The first two are fixed ascloud.meraki. The third level identifies the type of events sent, and the fourth level indicates the event subtype.
...
Technology
...
Brand
...
Type
...
Subtype
...
cloud
...
meraki
...
api
...
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service |
|---|
Tags | Data |
|---|
tables | |
|---|---|
Cisco Meraki |
|
|
|
How is the data sent to Devo?
To send logs to these tables, Devo provides a collector that you can download and use to send the required events to your Devo domain. You can learn how to use it in Cisco Meraki collector.
Table structure
These are the fields displayed in this table:
cloud.meraki.api.changelog
Field | Type | Extra fields |
|---|---|---|
eventdate |
| |
hostname |
| |
ts |
| |
adminName |
| |
adminEmail |
| |
adminId |
| |
page |
| |
label |
| |
oldValue |
| |
newValue |
| |
hostchain |
| ✓ |
tag |
| ✓ |
rawMessage |
| ✓ |