| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
The tags beginning with network.meraki identify events generated by Cisco Meraki Network Security products.
Valid tags and data tables
The full tag must have at least 3 levels. The first two are fixed asnetwork.meraki. The third level identifies the type of events sent. The fourth, fifth, and sixth levels indicate the event subtypes and are used in thenetwork.meraki.api tags.
...
Technology
...
Brand
...
Type
...
Subtype
...
Subtype
...
Subtype
...
network
...
meraki
...
api
...
<subtype>
...
<version>
...
<format>
...
events
flows
ids-alerts
urls
airmarshal_events
switch
security_event
...
-
...
-
...
-
These are the valid tags and corresponding data tables that will receive the parsers' data:
...
Tag
...
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
|---|---|---|
|
| |
| ||
| ||
| ||
|
| |
| ||
|
| |
|
| |
| ||
|
| |
|
| |
| ||
| ||
| ||
| ||
|
| |
|
| |
|
|
How is the data sent to Devo?
To send logs to the network.meraki.api.events and network.meraki.api.security_events 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.
...