Dashboard URLs

[JoelKelley]

Hey there - we are working on Dashboard API integration and among other things we're creating a monitoring engine that will open NOC tickets as necessary and I want to make our NOC techs' lives as easy as possible by dropping in a Dashboard URL in to the NOC ticket for the network or device in question.  I don't see any way to do this with the calls currently available in Dashboard API.  If you look at the page source on a Appliance Status Page you'll find a variable called "Mkiconf.ng_eid" that appears to the be what I'll call the network's sub-device group identifier.  And this "eid" is the one thing I need to be able to dynamically generate a Dashboard URL. 

Anyone have any tips?

[PhilipDAth]

This URL is often used on the local status page of a switches, but it does not always seem to work for me:

https://dashboard.meraki.com/manage/dashboard/show?mac=xx:xx:xx:xx:xx:xx&port=yy

[JPena]

I get what you're trying to do, but not sure if I would rely on the dashboard URLs to be consistent.

[MilesMeraki]

Surely you could just setup SMTP alerting to go to a email address which is integrated with your NOC ticketing system. The SMTP alerts from Meraki come with a hyperlink embedded to the devices dashboard URL.  

[JoelKelley]

We do that some today but there are all sorts of problems with this approach... those emails don't always come through and the don't always come on time either.

[DaveRey]

Did this ever get an answer?  I'd like to link to a device status page, but don't see any info about generating the URL.

Cheers

[DaveRey]

Silly me... a little more searching and I would have found it... doh

https://developer.cisco.com/meraki/build/deep-links/

[DaveRey]

Well... reply to my own reply... I see that I can get a list of all the network EID's but I can't figure out how to do it from a script/api. I use Perl and Curl for my api access and it works great for me, but I haven't been able to use it get things from the dashboard website itself. Meaning stuff you have to be logged in to get. So I have to log in to get the Org JSON data, then save that locally and use the local data for my scripts. So of course it will be out of date as soon as we add or remove a network in our org.

I don't really want to switch to python if I don't have to. Remember when being a network admin/designer didn't require advanced knowledge of web scripting? 😉

[joshand]

You should check https://dashboard.meraki.com/api_docs/v1#devices. "url" should now be there for deep-linking to the devices. Samples haven't been updated yet, but the value should be there.

$ curl --silent -L -H "X-Cisco-Meraki-API-Key: <key>" https://api.meraki.com/api/v0/organizations/710305/networks/L_578149602163690687/devices/Q2KN-XXXX-X... | jq

{

  "lat": 37.4180951010362,

  "lng": -122.098531723022,

  "address": "",

  "serial": "Q2KN-XXXX-XXXX",

  "mac": "0c:8d:db:xx:xx:xx",

  "wan1Ip": "x.x.x.x",

  "wan2Ip": null,

  "lanIp": "x.x.x.x",

  "url": "https://n27.meraki.com/Dynamic-Access-C/n/GmdI2aB/manage/nodes/new_list/13803413613080",

  "networkId": "L_578149602163690687",

  "name": "dCloud DAC MX",

  "model": "MX64",

  "firmware": "wired-15-14",

  "floorPlanId": null

}