Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Service description

Cisco Meraki offers the only solution that provides unified management of mobile devices, Macs, PCs, and the entire network from a centralized dashboard. Enforce device security policies, deploy software and apps, and perform remote, live troubleshooting on thousands of managed devices.

Cisco Meraki products are built from the ground up for cloud management and come out of the box with centralized management, layer 7 device and application visibility, real-time web-based diagnostics, monitoring, reporting, and much, much more.

Data source description

Source

Description

Devo data tables

Meraki organization changelog

Displays changes made in any network within the current Organization since it was created. This includes configuration changes made to all types of devices, not just administrative changes to the Dashboard. Each time a change is made an event in the ChangeLog will be generated.

cloud.meraki.api.changelog

MX security events

Display security events generated by MX Appliances for each existing network.
These events are logged as a result of the Connection Monitoring tests failing.

network.meraki.api.security_events

Appliance/Switch/Wireless Event Log

Display network events generated by all managed MR/SM/MS/MV devices for each existing network.

 network.meraki.api.events

For more info about the Cisco Meraki, visit the Cisco Meraki user guide.

Setup

Meraki collector works over the API to retrieve the data, so is needed to enable the access via API Key and generate a Key to allow the collector get the data following the steps below:

  1. Log in to your Meraki account

  2. Go to Organization → Settings.

  3. Go to the API Access Dashboard and tick the checkbox Enable access to the Cisco Meraki Dashboard API.

  4. Once you have enabled access to the API, we need to create the API Key. To do this, click the profile link below the checkbox, or by clicking your username and selecting your username, and clicking My Profile.

  5. Go to API Access → API Keys and click Generate New API Key.

  • If Meraki dashboard IP filtering is enabled, make sure to allow access for the collector IP or IP range.

  • Be careful, the API key will inherit the permissions of the user who creates it, so it must be created with a user with at least "organization - read only" permissions.

Run the collector

Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).

Change log for 1.x.x

Release

Released on

Release type

Details

Recommendations

v1.3.0

FEATURE VULNS IMPROVEMENTS

New features:

  • The resilience has been improved with a new feature that restart the collector when the Devo connections is lost and it cannot be recovered.

Improvements:

  • The underlay IFC SDK has been updated to v1.1.3.

Vulnerabilities mitigation:

  • All critical and high vulnerabilities have been mitigated.

Upgrade

v1.3.2

VULNS

Vulnerabilities mitigation:

  • All critical and high vulnerabilities have been mitigated.

Upgrade

v1.3.4

IMPROVEMENTS BUG FIX

Improvements:

  • When the Meraki API returns an HTTP CODE 429 (Too many requests), the collector handle it to avoid overflooding.

Bug fixes:

  • Some error messages were logged at the debug level and are now logged at the error level correctly.

Upgrade

v1.3.5

IMPROVEMENTS BUG FIX

Improvements:

  • The number of debug traces has been increased to provide better visibility when troubleshooting.

Bug fixes:

  • Logging AssertionError trace thrown when requesting invalid product types from networks without those product types is now logged in debug level.

Upgrade

v1.3.6

IMPROVEMENTS BUG FIX

Improvements:

  • The number of debug traces has been increased to provide better visibility when troubleshooting.

  • The network_security_events (MX) service has been enhanced with new logic that avoids requesting MX events from networks without MX appliances. This reduces the number of unnecessary API requests to Meraki that were returning 400 HTTP CODE.

  • Meraki Python package has been upgraded from v1.18.2 to v1.22.1

  • The events are sent to Devo in batches, increasing the performance.

Bug fixing:

  • Fixed a bug where the data extraction services via network_event_log and network_security_events stopped pulling events after retrieving the first page of 1,000 events. This behavior was causing some delay in the ingest in networks with a high volume of events.

  • Fixed how persistence of the network_security_events service is handled and it now stores a unique save point for each available network instead of one for all networks.

  • Fixed a bug where events were being sent to Devo without proper ordering. Now all events are ordered from the origin by the API.

Recommended version

  • No labels