DumbMonit
Monitorare Cisco Meraki con DumbMonit
BetaA Cisco Meraki organization through the Dashboard API: devices offline, Internet uplinks that failed, license out of compliance or expiring, clients per network.
DocumentazioneSito ufficiale: Cisco Meraki
Le descrizioni sono in inglese, come nel prodotto. Le etichette della pagina seguono la tua lingua.
Cosa controlla DumbMonit
A Cisco Meraki organization through the Dashboard API: devices that are offline, Internet uplinks of the MX routers that failed (and the failover to the other uplink), a license out of compliance or about to expire, and the number of clients per network. This integration is written from Cisco's Dashboard API documentation and has not been tested on real Meraki equipment. Every call is a read. Tell us what breaks.
Uso tipico. Beta. Meraki cloud: devices offline, failed Internet uplinks, license state and expiry, clients per network
Esempi
- Meraki MX / MS / MR
- Cisco Meraki cloud dashboard
Come si collega
Cosa serve
- API keyThe key of the read-only administrator created for DumbMonit, sent as a bearer token.
Porte di rete da aprire
443/TCPMeraki Dashboard API (HTTPS, api.meraki.com)
Passaggi di configurazione: Create a read-only API key for DumbMonit
In the Meraki dashboard, open Organization → Settings and tick Enable access to the Cisco Meraki Dashboard API.
Open Organization → Administrators → Add admin and create an administrator dedicated to DumbMonit, with Organization access set to Read-only.
[email protected]Sign in as that administrator, open My profile → API access and click Generate new API key. Copy it: the dashboard shows it only once.
In DumbMonit, enter api.meraki.com as the address and paste the key as API key. Leave Organization empty to read the first organization the key sees.
Attenzione. A dormant device (not seen for a long time) is counted but never reported as down, and a WAN socket without a cable is not a failed uplink: only an uplink that lost its Internet access is.