API Return on vpnstatus missing latency information

Solved
FInalStar
Comes here often

API Return on vpnstatus missing latency information

Is anyone else missing the the API return for the vpnstats where it doesn't include the latency information?

 

The documentation shows I should get a return that looks like this:

 

[
    {
        "networkId": "N_12345678",
        "networkName": "San Francisco Office",
        "merakiVpnPeers": [
            {
                "networkId": "L_23456789",
                "networkName": "New York Office",
                "usageSummary": {
                    "receivedInKilobytes": 1234567,
                    "sentInKilobytes": 2345678
                },
                "latencySummaries": [
                    {
                        "senderUplink": "wan1",
                        "receiverUplink": "wan1",
                        "avgLatencyMs": 15,
                        "minLatencyMs": 10,
                        "maxLatencyMs": 30
                    },
                    {
                        "senderUplink": "wan2",
                        "receiverUplink": "wan1",
                        "avgLatencyMs": 15,
                        "minLatencyMs": 10,
                        "maxLatencyMs": 30
                    }
                ],
                "lossPercentageSummaries": [
                    {
                        "senderUplink": "wan1",
                        "receiverUplink": "wan1",
                        "avgLossPercentage": 0,
                        "minLossPercentage": 0,
                        "maxLossPercentage": 0.1
                    },
                    {
                        "senderUplink": "wan2",
                        "receiverUplink": "wan1",
                        "avgLossPercentage": 0,
                        "minLossPercentage": 0,
                        "maxLossPercentage": 0.1
                    }
                ],
                "jitterSummaries": [
                    {
                        "senderUplink": "wan1",
                        "receiverUplink": "wan1",
                        "avgJitter": 0.01,
                        "minJitter": 0,
                        "maxJitter": 0.25
                    },
                    {
                        "senderUplink": "wan2",
                        "receiverUplink": "wan1",
                        "avgJitter": 0.01,
                        "minJitter": 0,
                        "maxJitter": 0.25
                    }
                ],
                "mosSummaries": [
                    {
                        "senderUplink": "wan1",
                        "receiverUplink": "wan1",
                        "avgMos": 4.1,
                        "minMos": 4,
                        "maxMos": 4.2
                    },
                    {
                        "senderUplink": "wan2",
                        "receiverUplink": "wan1",
                        "avgMos": 4.1,
                        "minMos": 4,
                        "maxMos": 4.2
                    }
                ]
            }
        ]
    },

 

But I only get this as a return:

[
    {
        "networkId": "N_12345678",
        "networkName": "San Francisco Office",
        "merakiVpnPeers": [
            {
                "networkId": "L_23456789",
                "networkName": "New York Office",
                "usageSummary": {
                    "receivedInKilobytes": 1234567,
                    "sentInKilobytes": 2345678
                },
            }
        ]
    }
]

 

Any help understanding why I am missing all the latency/connection info would be greatly appreciated

1 Accepted Solution
Ryan_Miles
Meraki Employee
Meraki Employee

By default you'll only see those stats when there are 2 WAN uplinks and therefore performance probes going across each WAN link. If you contact Support single link monitoring can be enabled which would show the extra fields in the API output.

View solution in original post

3 Replies 3
Ryan_Miles
Meraki Employee
Meraki Employee

By default you'll only see those stats when there are 2 WAN uplinks and therefore performance probes going across each WAN link. If you contact Support single link monitoring can be enabled which would show the extra fields in the API output.

GIdenJoe
Kind of a big deal
Kind of a big deal

Oh, I didn't know you could get that enabled on a single link.

The answer I got once on the phone was that it was not doing that for single links.

FInalStar
Comes here often

Thank you so much for the help. That worked great

Get notified when there are additional replies to this discussion.