This section guides you through setting up, configuring, and managing the Cisco Meraki integration in OpsRamp.
Prerequisites
- Provide required discovery inputs: organizationId, merakiApiKey
- Expose the HTTP/HTTPS administration endpoints referenced by the SDK for inventory and monitoring.
- Permit SSH access for any command-based collection paths discovered in the SDK source.
Configure Cisco Meraki Integration
Click here to Configure and Install the Cisco Meraki Integration
- To select your client, navigate to All Clients, and click the Client/Partner dropdown menu. Note: You may either type your client’s name in the search bar or select your client from the list.
- Navigate to Setup > Account. The Account Details screen is displayed.
- Click Integrations. The Installed Integrations screen is displayed with all the installed applications. Note: If you do not have any installed applications, you will be navigated to the Available Integrations and Apps page with all the available applications along with the newly created application with the version.
- Click + ADD on the Installed Integrations page. Note: Search for the integration either by entering the name of the integration in the search bar or by selecting the category of the integration from the All Categories dropdown list.
- Click ADD in the Cisco Meraki application.
- In the Configuration screen, click + ADD. The Add Configuration screen appears.
- Enter the following BASIC INFORMATION.
| Field Name | Description | Field Type |
|---|---|---|
| Name | A unique name to identify this Cisco Meraki integration instance in OpsRamp. Used to distinguish multiple configurations if monitoring more than one Meraki organization. | String |
| Meraki API Host/IP | The Meraki Dashboard API endpoint hostname or IP address (typically api.meraki.com). | String |
| Is Secure | Enable HTTPS (TLS) communication with the Meraki API. Should be set to true (port 443). | Checkbox |
| Port | The network port used to connect to the Meraki API. Default: 443. | Integer |
| Meraki API Key | The API key generated from the Meraki Dashboard (Organization → Settings → API access). Grants read access to organization, network, and device data. | String |
| Confirm Meraki API Key | Re-enter the API key to confirm it was typed correctly. | String |
| Meraki Organization ID | The numeric Organization ID from the Meraki Dashboard. Scopes discovery and monitoring to a specific organization. Found via Dashboard → Organization → Settings or the GET /organizations API. | String |
| API Timeouts | Enable or disable custom API timeout handling. When disabled, defaults apply (connection: 60s, request: 60s, socket: 60s). Enable to override with custom values. | Checkbox |
| App Failure Notifications | Enable or disable alert notifications when the integration itself encounters failures (e.g., authentication errors, API unreachable). Helps detect integration health issues. | Checkbox |
| Event/Alert Polling | Enable or disable polling of Meraki events (device status changes, VPN connectivity changes, port status) and mapping them to OpsRamp alerts based on the configured severity mapping. | Checkbox |
- CUSTOM ATTRIBUTES: Custom attributes are the user-defined data fields or properties that can be added to the preexisting attributes to configure the integration.
| Field Name | Description | Field Type |
|---|---|---|
| Custom Attribute | Select the custom attribute from the dropdown. You can add attributes by clicking the Add icon (+). | Dropdown |
| Value | Select the value from the dropdown. | Dropdown |
Note
The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).- In the RESOURCE TYPE section, select:
- ALL: All the existing and future resources will be discovered.
- SELECT: You can select one or multiple resources to be discovered.
- In the DISCOVERY SCHEDULE section, select recurrence pattern to add one of the following patterns:
- Minutes
- Hourly
- Daily
- Weekly
- Monthly
- Click ADD.
Note
Sample values shown in the configuration fields are for illustration purposes only. Use your actual integration details when configuring.Now the configuration is saved and displayed on the configurations page after you save it.
Note
From the same page, you may Edit and Remove the created configuration.- Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.
Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries. - Click NEXT.
- (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.
- Select an existing registered profile.
- Click FINISH.
The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.
Modify Cisco Meraki Integration
See Modify an Installed Integration or Application article.
Note: Select the Cisco Meraki application.
Discover Resources in Cisco Meraki Integration
Click here to View the Cisco Meraki Details
To discover resources for Cisco Meraki:
- Navigate to Infrastructure > Search > WIFI NETWORK > Cisco Meraki.
- The Cisco Meraki page is displayed, select the application name.
- The RESOURCE DETAILS page appears from the right.
- Click the ellipsis (…) on the top right and select View details.
- Navigate to the Attributes tab to view the discovery details.
View resource metrics
To confirm Cisco Meraki monitoring, review the following:
- Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
- Alerts: Alerts are generated for metrics that are configured as defined for integration.
- Click the Metrics tab to view the metric details for Cisco Meraki.
×![]()