If you do not see the 2 roles 'IDS Alerts' and 'Security events' from your dashboard, then you cannot leverage them in the API as roles. I am able to use the Security events role in my syslog settings through the API across several branch locations for one of my clients, all which consist of combined networks (wireless/switch/security).    It is unusual that 'Security events' is not a selectable role, so I would open a case with Meraki support to have them check out what could be going on; I am unsure on the 'IDS alerts' role as I've never seen that as an option in the dashboard, and in the current API library, I do not see that as a role option either. ... View more

I've seen it take longer than 10 minutes. Best to give it 20min wait. ... View more

@PhilipDAth thanks for the reply.   Even if I set single_request_timeout to 300 seconds or any other value, I get back a gateway error from the api after 60 seconds. That's probably where the hard limit is for the api, so we can not set it to a bigger value than 60 seconds. ... View more

hi. I managed to work around this by using the startingAfter parameter (although documentation says that client should not use this). It seems that if I don't do it, Meraki will try to do a full extract. Some of the clients with highest traffic causes it to crash ... View more

Thank you for your reply. I too was getting inconsistent behavior when trying to get real time snapshot, so instead I switched to getting the snapshot 5 mins before current time. That is OK for my requirements.   The thing I noticed with that method is, as I need to provide a timestamp to get the snapshot at a specific time, is that the API accepts timestamp parameter in Los Angeles timezone. ... View more