[ZBXNEXT-6844] Cisco Meraki integration out of the box Created: 2021 Aug 20  Updated: 2024 Apr 10  Resolved: 2022 Nov 16

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Documentation (D), Frontend (F), Server (S), Templates (T)
Affects Version/s: 6.0 (plan)
Fix Version/s: 6.0.11rc1, 6.2.5rc1, 6.4.0beta3, 6.4 (plan)

Type: New Feature Request Priority: Critical
Reporter: Edgar Akhmetshin Assignee: Andrew Biba
Resolution: Fixed Votes: 6
Labels: Cisco, Meraki
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
Duplicate
Sub-task
Team: Team INT
Sprint: Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022)
Story Points: 14

 Description   

https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API

https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/

Please add official itnegration with resource discovery and monitoring.



 Comments   
Comment by Zachariah A DeGraaf [ 2022 Oct 18 ]

I really interested to see how you would be able to implement better monitoring of Meraki devices via the API in a scalable way. I wrote up a bash external script that does the monitoring, but it is rather messy. Anyone interested can view my code here

The biggest roadblock that I ran into was Meraki's hard API limit, it forced me to use the API queries that pulled larger datasets, then merge the datasets together into one large JSON object. 

Comment by Alexander Vladishev [ 2022 Nov 08 ]

Available in:

Comment by Morten Bech Christensen [ 2023 Feb 13 ]

This template would have been so much better if ZBXNEXT-1527 was selected for development.

Then all the JavaScript code could be substituted with Host Prototypes for Networks, that then could create devices using nested Host Prototypes

Please reconsider where time is spent - Templates done badly or a greater platform - ZBXNEXT-1527 should be prioritised - please

 

Generated at Fri May 23 08:57:06 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.