Meraki Monitoring Maximised Using Meraki Dashboard APIs – The Highlight Advantage

Discover how to maximize Meraki monitoring using APIs, enhancing network performance and reliability through proactive issue resolution.

APIs have emerged as an indispensable tool those managing large scale networks. They offer a structured approach to automate and streamline network operations, enabling different applications to communicate and function effectively. In the context of network management, APIs enable tasks such as deployment, configuration, as well as monitoring and assurance, all of which are crucial for maintaining robust and scalable networks.

Ongoing monitoring and assurance

Once a network is deployed, maintaining its health and performance is critical. APIs play a key role in ongoing monitoring by providing access to real-time data. This data can include status information, such as whether a particular location is online or offline, as well as performance metrics like data throughput and the number of connected clients.

Services like Highlight use Meraki APIs, amongst other technologies, to collect vast amounts of data from the network, offering insights that aid in proactive management and troubleshooting. By harnessing APIs, Highlight and its customers can ensure their networks operate optimally and can quickly address any potential issues.

The importance of understanding API rate limits for Meraki monitoring

While APIs offer significant advantages, it’s essential to use them responsibly to maintain system integrity and ensure the fair use of resources.

APIs are often subject to rate limits, restricting the number of API calls that can be made within a specific timeframe, such as 10 calls per second in the example of Cisco’s Meraki Dashboard. Exceeding these limits can lead to requests being rejected, not only for the offending application but also for other apps relying on the same API.

Being a good API citizen involves minimising the impact of your API interactions by only making efficient and necessary calls, thereby conserving resources and ensuring availability for all users.

How to be a good API citizen

Being a good API citizen not only optimises your operations but also contributes to a sustainable and cooperative digital ecosystem.  The overall aim is to leave the smallest possible impact or footprint for the tasks being undertaken. Here are some points to consider:

1. Define data requirements: Clearly identify what information is needed and the optimum frequency for data retrieval or updates against an API’s call rate limits. Collecting data too infrequently may result in outdated insights, while excessive requests will strain resources.
2. Understand the API functionality: Understanding the API’s capabilities is essential. For example, you may want information on all access points across a Cisco Meraki network of 10,000 devices. Rather than make individual device-based calls, it is far more efficient to make a single API call per network location or organisation wide.
3. Set a logical sequence for data retrieval: There should be a logical and pragmatic sequence to collecting information. For example, using a tree diagram, identify if a device is up or down first before querying how many people are connected. The sequence should stop if the information is irrelevant whilst leaving the least important data until last in the event that if call rate limits are reached and calls are delayed, only the least important data is missed.
4. Use query parameters: Query parameters enable users to narrow down the data retrieved to focus only on what’s necessary. For instance, when seeking the status of Wi-Fi access points, set parameters to exclude unrelated devices like switches or firewalls, thereby reducing unnecessary volumes of data and processing time.
5. Monitor rate limits and responses: Pay close attention to rate limit responses, such as HTTP status code 429 (“Too Many Requests”). This indicates that the API is being overwhelmed, prompting a need to review and adapt the frequency of requests.
6. Assess API load and collaborate with stakeholders: Continuously monitor API usage to ensure that your applications are not monopolising resources. Collaborate with other stakeholders who might be accessing the same APIs to coordinate usage patterns and prevent conflicts.
7. Consider alerting webhooks for event-driven updates: Instead of polling for updates, webhooks can be used to push relevant information as events occur. This method reduces the need for constant querying. However, reliance on webhooks requires trust that all important information has been delivered.
8. Be prepared to fail: API endpoints are like all online services and may occasionally respond slowly or not at all. Additionally, vendors may update their API specifications and respond with additional data. Be prepared for failure and fail gracefully so your application can continue to work when problems arise.
9. Stay informed on API changes: APIs are constantly evolving. Review API updates on a regular basis to ensure you benefit from the latest best practices and features. It’s not uncommon for vendors to deprecate API calls, often replacing them for faster and more efficient alternatives. Discover where the vendor announces such changes and regularly check to ensure you’re not out of date.

Enhancing Meraki monitoring with the Highlight Service Observability Platform

While working directly with Meraki APIs can be powerful, it requires significant development effort and ongoing maintenance. The award-winning Highlight Service Observability Platform offers a pre-made efficient solution by seamlessly integrating with Meraki’s Dashboard API to provide comprehensive monitoring capabilities:

1. Rapid Integration: Create an API key in your Meraki instance, input it into Highlight, and within minutes, the platform discovers and starts collecting data on your Meraki SD-WAN, switches, cellular and WiFi devices.
2. Unified Visibility: Gain real-time and historical visibility of Meraki device performance alongside other network components in a single, intuitive interface.
3. Efficient Problem Identification: Utilize color-coded status indicators and customisable views to quickly pinpoint issues across your Meraki estate.
4. Comprehensive Reporting: Generate detailed reports on Meraki device performance, helping you make data-driven decisions about your network.
5. Multi-vendor Support: Seamlessly incorporate Meraki monitoring into complex network environments with standardised metrics across different vendors.

The Highlight Advantage for Meraki Monitoring

Highlight is an approved solution on the Cisco Networking Marketplace with proven results across thousands of organisations. By adopting the Highlight Service Observability Platform, organizations can transform complex Meraki network data into actionable insights:

1. Scalable Monitoring: Network visibility that scales easily as your network estate grows in size and complexity.
2. Proactive Management: Identify trends and isolate IT issues consistently, improving overall network performance.
3. Enhanced Communication: Foster clear communication between network management staff and end-users at all levels.
4. Optimised IT Support: Improve support efficiency and reduce time-consuming escalations.