Hi @sungod and Community!    First – thanks for raising this as a topic. While we initially designed the read-only role to include a user's ability to troubleshoot, and port cycle (along with all live tools) is seen as falling into that permissible category, we also fully recognize that this may or may not be the desired behavior based on your own organizational IT policies.   We are reviewing and further evaluating how we may add an explicit option to enable or disable this so to put this decision in our users' hands. We'll follow up when we have an update to share to address this concern and feedback.     Thanks for being Meraki MS customers, we value each of you. Be in touch!   ~tony Product Management, Meraki Switching ... View more

Indeed, thanks for the report and more importantly for opening up a case – that ensures we are getting the report over so we can fix these types of issues for our devs out there 🙂 ... View more

Thanks for the report, we will track and get this fixed. ... View more

You can check out the recent integration that DD created for Meraki here:. It is a crawler for pulling network event logs into DD: https://docs.datadoghq.com/integrations/meraki/ ... View more

Just to follow up, we released the Event Log via API in November: https://developer.cisco.com/meraki/api/#/rest/api-endpoints/events/get-network-events ... View more

Hi everyone – this is expected, once you have accepted the terms we will then add you and you'll receive a welcome note, after which you should be able to log in! ... View more

OP: from your most it sounds like you want alerts via the API. I suggest you take a look at webhooks for Airmarshal: https://developer.cisco.com/meraki/webhooks/#webhook-sample-alerts/sample3 first Regarding the errors you're hitting, try including the ?productType=wireless parameter as well: https://api.meraki.com/api/v0/networks/:networkId/events?productType=appliance&includesEventType=failover_event I'm verifying but I believe productType is actually a required parameter, and we need to update our docs to reflect that. ... View more

@dbd Could you elaborate on what you are trying to do, create or build with our API? Any details would be appreciated. We're considering a feature that that matches what you're asking for. Thanks, Tony ... View more

This was a cloud-based change, does not require any firmware changes. ... View more

Hi @maizumi! That is a new feature and enhancement to the Motion Alert – You can read more about it in our documentation via the link below, but in a nutshell it provides you with a link to the image that was captured when the motion event was triggered. If you are encountering a situation where the image was not accessible, please open a case and report that issue, so we can investigate. We'll also get this attribute defined and added to our webhook API documentation so it's clear. https://documentation.meraki.com/MV/Advanced_Configuration/Motion_Alerts Best, The Meraki API team </ > ... View more

We just pushed a change that allows an array of orders / serials / licenses via the claim endpoint directly! Docs will get updated but if you want to try it out now, here are the supported parameters (notice they are now plural, and formatted as an array): https://dashboard.meraki.com/api_docs#claim-a-list-of-devices-licenses-and/or-orders-into-an-organization #wishgranted 😉 ... View more

We recently published a sample for all Webhook alerts. You can see them here: https://developer.cisco.com/meraki/webhooks/#!webhook-sample-alerts We'll fix the broken link, thanks for reporting!  ... View more

Nice!!! We published this in our shiny new Developer Hub that went live this week: https://developer.cisco.com/meraki/explore/tag-based-ipsec-vpn-failover/    @Guillaume6hat seems we may want to merge your changes to the original script and get it into GitHub, they make it even better 😄   ... View more

Take a look at these two endpoints, they're purpose built for your use case. Let us know if you have any feedback!   Org-wide loss/latency, last 5 samples https://dashboard.meraki.com/api_docs#return-the-uplink-loss-and-latency-for-every-mx-in-the-organization-from-2---7-minutes-ago   Device loss/latency timeseries https://dashboard.meraki.com/api_docs#get-the-uplink-loss-percentage-and-latency-in-milliseconds-for-a-wired-network-device   ... View more

Thanks for the report, we have reproduced and will address. For now omitting the application-type header appears to address as @jdsilva indicated ... View more

For those interested in the latest and greatest on our APIs, bookmark this for a comprehensive API changelog! https://create.meraki.io/whats-new/       - Tony PM, API & Developer Ecosystem   ... View more

Hi @bowersjj,   The sandbox is alive and well! Check it out here, search for "Meraki": https://devnetsandbox.cisco.com/RM/Topology ... View more

Hi AlexB, Z3 will be available end of the month. Thanks for your patience! ... View more

All,   I have submitted this to our product/engineering team, will keep everyone posted but no need to make additional submissions. ... View more