Meraki MX Tunnel Stats when not Auto VPN

[Prodrick]

What stats should one expect from this endpoint when the tunnel is not an Auto VPN (i.e. between an MX84 in one Meraki Org and an MX450 in another org, or between an MX84 and a Cisco ASA)?  I'm only seeing data for "receivedInKilobytes" and "sentInKilobytes" and NOT latency, packet loss, jitter, and MOS stats for these, and wanted to know if that was an expected limitation.

Thanks.


https://api.meraki.com/api/v1/organizations/:organizationId/appliance/vpn/stats

[Badr-eddine]

I think the reason for this limitation is that Meraki MX devices primarily provide traffic and data usage statistics, focusing on monitoring and managing network traffic rather than providing detailed network performance metrics like latency, packet loss, jitter, and MOS scores.

[alemabrahao]

As far as I know it will only return the Auto VPN status, for non-Meraki peers it is not possible to return this information.

[Prodrick]

However disappointing, that seems to align with what we are seeing. 

[ww · Accepted solution]

You can only see this for autovpn when there are 2 uplinks used. (3rd party vpn only uses 1) Meraki sends probes in the autovpn and Its used for sdwan policies 

https://documentation.meraki.com/MX/Monitoring_and_Reporting/SD-WAN_Monitoring#How_are_these_metrics...

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/...

[Prodrick]

@ww, thanks this is very informative and answered my question completely.