This article explains how to configure the Experience Monitoring integration for Cisco Meraki.
The Cisco Meraki integration provides bi-directional communication utilized for Experience Monitoring. This enables seamless visibility into network and device performance across your environment. This connector brings events, telemetry, and IoT inventory data directly into the Cato platform, streamlining troubleshooting and device management. Gain faster insights, reduce mean time to resolution, and improve digital experience for all connected users and devices.
To configure this integration, you need to:
- Configure the integration in your Meraki Dashboard
- Create the API connector in the Cato Management Application (CMA)
To create the Cisco Meraki integration, create the required information in the Meraki Dashboard.
-
A Cisco Meraki Dashboard account with
- Read-only access at the organization level
- API access enabled (you can enable is by navigating to Organization > Settings > Dashboard API access)
In the Meraki Dashboard, create an API key to be entered into the CMA.
To configure the Meraki Integration:
- Log in to the Meraki Dashboard.
- Navigate to Organization > Settings.
- Under the Dashboard API access section, enable Enable access to the Cisco Meraki Dashboard API.
- Click Save.
- Navigate to Organization > API & Webhooks.
- On the API keys and access tab, click Generate new API key.
-
Copy and save the API key so it can be entered into the CMA.
Note: The API key inherits the permissions of the admin account that generated it.
After you have set up an integration, add the details in the CMA.
To create the API connector in the CMA:
- From the navigation menu, click Resources > Integrations.
- Click the Configured Integrations tab.
-
Click New.
The New Integration panel opens.
- Select the SaaS Application you want to add.
- In the Capability drop down select Device Management.
- Add the details created during step one.
- Click Save.
- The app is visible on the Integrated Apps table with a Connected status.
0 comments
Article is closed for comments.