<?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 Inability to Prisma Access SD-WAN Metrics via API Endpoints in Prisma SD-WAN Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/606834#M202</link>
    <description>&lt;P&gt;I am experiencing issues accessing Prisma SD-WAN metrics through the API on multiple versions.&lt;/P&gt;
&lt;P&gt;While certain API endpoints, such as those related to site and device configurations, are functioning correctly, I am unable to retrieve data from metrics-related endpoints.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here are the specifics:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Working API Example:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v4.10/api/sites/{site-id}&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2na" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745%27" href="https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/xxx'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' -s| jq -r '._status_code'&lt;/LI&gt;
&lt;LI&gt;Command Output: 200&lt;/LI&gt;
&lt;LI&gt;A successful 200 OK status with details for a specific site (id: xxx), including its configuration and location, confirms that my token and other configuration aspects are correct.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Failing API Example 1:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v2.3/api/monitor/sys_metrics&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2nc" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics%27" href="https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' | jq&lt;/LI&gt;
&lt;LI&gt;Command Output: No Output&lt;/LI&gt;
&lt;LI&gt;Issue: No response or data returned&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Failing API Example 2:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v2.1/api/monitor/aiops/aggregates&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2ne" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates%27" href="https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' | jq&lt;/LI&gt;
&lt;LI&gt;Command Output: { "_status_code": "404", "_info": [ { "code": "ROUTE_NOT_FOUND_0001", "message": "ROUTE_NOT_FOUND_0001: /v2.1/api/tenants/xxx/monitor/aiops/aggregates" } ] }&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These errors suggest that either the routes for metrics APIs are unavailable or misconfigured.&lt;/P&gt;
&lt;P&gt;I have checked the relevant documentation &lt;A id="menur2ng" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://pan.dev/sdwan/api/metrics/" href="https://pan.dev/sdwan/api/metrics/" target="_blank" rel="noreferrer noopener" aria-label="Link https://pan.dev/sdwan/api/metrics/"&gt;https://pan.dev/sdwan/api/metrics/&lt;/A&gt; and confirmed my implementation matches the expected usage.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please advise on any steps to resolve this or confirm whether these API endpoints are functional in the current release.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Oct 2024 08:41:23 GMT</pubDate>
    <dc:creator>K.Jrva</dc:creator>
    <dc:date>2024-10-18T08:41:23Z</dc:date>
    <item>
      <title>Inability to Prisma Access SD-WAN Metrics via API Endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/606834#M202</link>
      <description>&lt;P&gt;I am experiencing issues accessing Prisma SD-WAN metrics through the API on multiple versions.&lt;/P&gt;
&lt;P&gt;While certain API endpoints, such as those related to site and device configurations, are functioning correctly, I am unable to retrieve data from metrics-related endpoints.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here are the specifics:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Working API Example:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v4.10/api/sites/{site-id}&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2na" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745%27" href="https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/1697453853563015745'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v4.10/api/sites/xxx'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' -s| jq -r '._status_code'&lt;/LI&gt;
&lt;LI&gt;Command Output: 200&lt;/LI&gt;
&lt;LI&gt;A successful 200 OK status with details for a specific site (id: xxx), including its configuration and location, confirms that my token and other configuration aspects are correct.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Failing API Example 1:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v2.3/api/monitor/sys_metrics&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2nc" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics%27" href="https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v2.3/api/monitor/sys_metrics'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' | jq&lt;/LI&gt;
&lt;LI&gt;Command Output: No Output&lt;/LI&gt;
&lt;LI&gt;Issue: No response or data returned&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Failing API Example 2:&lt;/STRONG&gt;
&lt;UL&gt;
&lt;LI&gt;Endpoint: GET /v2.1/api/monitor/aiops/aggregates&lt;/LI&gt;
&lt;LI&gt;Command: curl -L '&lt;A id="menur2ne" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates%27" href="https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates%27" target="_blank" rel="noreferrer noopener" aria-label="Link https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates'"&gt;https://api.sase.paloaltonetworks.com/sdwan/v2.1/api/monitor/aiops/aggregates'&lt;/A&gt; -H "Authorization: Bearer $TOKEN" -H 'Accept: application/json' | jq&lt;/LI&gt;
&lt;LI&gt;Command Output: { "_status_code": "404", "_info": [ { "code": "ROUTE_NOT_FOUND_0001", "message": "ROUTE_NOT_FOUND_0001: /v2.1/api/tenants/xxx/monitor/aiops/aggregates" } ] }&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These errors suggest that either the routes for metrics APIs are unavailable or misconfigured.&lt;/P&gt;
&lt;P&gt;I have checked the relevant documentation &lt;A id="menur2ng" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://pan.dev/sdwan/api/metrics/" href="https://pan.dev/sdwan/api/metrics/" target="_blank" rel="noreferrer noopener" aria-label="Link https://pan.dev/sdwan/api/metrics/"&gt;https://pan.dev/sdwan/api/metrics/&lt;/A&gt; and confirmed my implementation matches the expected usage.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please advise on any steps to resolve this or confirm whether these API endpoints are functional in the current release.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 08:41:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/606834#M202</guid>
      <dc:creator>K.Jrva</dc:creator>
      <dc:date>2024-10-18T08:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: Inability to Prisma Access SD-WAN Metrics via API Endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/615923#M205</link>
      <description>&lt;P&gt;I've found that metrics-related API endpoints are functional using the POST method instead of GET.&lt;/P&gt;
&lt;P&gt;Here’s an example that successfully retrieves metrics data:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;url="https://api.sase.paloaltonetworks.com/sdwan/monitor/v2.0/api/monitor/sys_point_metrics"
token="YOUR_BEARER_TOKEN"
site_id="YOUR_SITE_ID"
element_id="YOUR_ELEMENT_ID"
current_time=$(date -u -d '-5 minutes' +"%Y-%m-%dT%H:%M:%S.000Z")

curl -X POST "$url" \
  -H "Authorization: Bearer $token" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "x-panw-region: europe" \
  -d '{
    "start_time": "'"$current_time"'",
    "interval": "5min",
    "metrics": [
      {
        "name": "MemoryUsage",
        "unit": "percentage"
      }
    ],
    "filter": {
      "site": "'"$site_id"'",
      "elements": [
        "'"$element_id"'"
      ]
    },
    "view": {}
  }'
&lt;/LI-CODE&gt;
&lt;P&gt;This command sends a POST request with the necessary payload to retrieve the MemoryUsage metric for the specified site and element.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 07:22:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/615923#M205</guid>
      <dc:creator>K.Jrva</dc:creator>
      <dc:date>2024-11-01T07:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: Inability to Prisma Access SD-WAN Metrics via API Endpoints</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/1242750#M327</link>
      <description>&lt;P&gt;You could use a python script like this one too:&lt;BR /&gt;&lt;A href="https://github.com/vladracs/prismasase/blob/main/scm_device_cpu_timeseries.py" target="_blank"&gt;https://github.com/vladracs/prismasase/blob/main/scm_device_cpu_timeseries.py&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 19:37:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-discussions/inability-to-prisma-access-sd-wan-metrics-via-api-endpoints/m-p/1242750#M327</guid>
      <dc:creator>VladFSousa</dc:creator>
      <dc:date>2025-11-27T19:37:58Z</dc:date>
    </item>
  </channel>
</rss>

