<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Appliance VPN Stats: per-uplink receivedInKilobytes and sentInKilobytes in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441679#M6515</link>
    <description>&lt;P&gt;Using the Dashboard API, we are able to monitor uplink status, traffic, and health, and are able to monitor per-uplink VPN stats like latency, jitter, packet loss, MOS... However, how might one monitor the per-uplink sent/received stats?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This endpoint seems to provide the relevant VPN stats data, but the sent/received stats are aggregated rather than separated by uplink like the rest of the stats. &lt;BR /&gt;&lt;BR /&gt;Thoughts?&lt;BR /&gt;&lt;BR /&gt;Thanks so much.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jul 2023 12:55:42 GMT</pubDate>
    <dc:creator>Prodrick</dc:creator>
    <dc:date>2023-07-12T12:55:42Z</dc:date>
    <item>
      <title>Appliance VPN Stats: per-uplink receivedInKilobytes and sentInKilobytes</title>
      <link>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441679#M6515</link>
      <description>&lt;P&gt;Using the Dashboard API, we are able to monitor uplink status, traffic, and health, and are able to monitor per-uplink VPN stats like latency, jitter, packet loss, MOS... However, how might one monitor the per-uplink sent/received stats?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This endpoint seems to provide the relevant VPN stats data, but the sent/received stats are aggregated rather than separated by uplink like the rest of the stats. &lt;BR /&gt;&lt;BR /&gt;Thoughts?&lt;BR /&gt;&lt;BR /&gt;Thanks so much.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 12:55:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441679#M6515</guid>
      <dc:creator>Prodrick</dc:creator>
      <dc:date>2023-07-12T12:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: Appliance VPN Stats: per-uplink receivedInKilobytes and sentInKilobytes</title>
      <link>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441680#M6516</link>
      <description>&lt;P&gt;Nobody?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 12:58:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441680#M6516</guid>
      <dc:creator>Prodrick</dc:creator>
      <dc:date>2023-07-14T12:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: Appliance VPN Stats: per-uplink receivedInKilobytes and sentInKilobytes</title>
      <link>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441681#M6517</link>
      <description>&lt;P&gt;How might other be achieving this?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 15:12:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/appliance-vpn-stats-per-uplink-receivedinkilobytes-and/m-p/5441681#M6517</guid>
      <dc:creator>Prodrick</dc:creator>
      <dc:date>2023-07-18T15:12:41Z</dc:date>
    </item>
  </channel>
</rss>

