https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407581#M1497 <P>Oh, I didn't know you could get that enabled on a single link.</P><P>The answer I got once on the phone was that it was not doing that for single links.</P> Wed, 06 Jul 2022 06:00:32 GMT joey.debra 2022-07-06T06:00:32Z https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407578#M1494 <P>Is anyone else missing the the API return for the vpnstats where it doesn't include the latency information?</P><P>The documentation shows I should get a return that looks like this:</P><PRE class="lia-code-sample language-json"><CODE>[ { "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 } ] } ] },</CODE></PRE><P>But I only get this as a return:</P><PRE class="lia-code-sample language-markup"><CODE>[ { "networkId": "N_12345678", "networkName": "San Francisco Office", "merakiVpnPeers": [ { "networkId": "L_23456789", "networkName": "New York Office", "usageSummary": { "receivedInKilobytes": 1234567, "sentInKilobytes": 2345678 }, } ] } ]</CODE></PRE><P>Any help understanding why I am missing all the latency/connection info would be greatly appreciated</P> Tue, 05 Jul 2022 23:00:09 GMT https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407578#M1494 FinalStar 2022-07-05T23:00:09Z https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407579#M1495 <P>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.</P> Tue, 05 Jul 2022 23:23:05 GMT https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407579#M1495 Ryan_Miles 2022-07-05T23:23:05Z https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407580#M1496 <P>Thank you so much for the help. That worked great</P> Tue, 05 Jul 2022 23:58:14 GMT https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407580#M1496 FinalStar 2022-07-05T23:58:14Z https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407581#M1497 <P>Oh, I didn't know you could get that enabled on a single link.</P><P>The answer I got once on the phone was that it was not doing that for single links.</P> Wed, 06 Jul 2022 06:00:32 GMT https://community.cisco.com/t5/network-platform-api/api-return-on-vpnstatus-missing-latency-information/m-p/5407581#M1497 joey.debra 2022-07-06T06:00:32Z