<?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 Re: selection criteria for alerts in API call to https://api.ca.prismacloud.io/v2/alert in Prisma Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/selection-criteria-for-alerts-in-api-call-to-https-api-ca/m-p/551782#M997</link>
    <description>&lt;P&gt;Hi Sergii,&lt;/P&gt;
&lt;P&gt;At a first look, this sounds like the expected behavior, to us a "change" means going from {never opened,open} to {dismissed,snoozed,resolved} within a time interval.&lt;/P&gt;
&lt;P&gt;However, let me take a closer look, can you reply with an example of retrieved alerts that demonstrate the problem, together with the query parameters you used?&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 14:43:10 GMT</pubDate>
    <dc:creator>JNeytchev</dc:creator>
    <dc:date>2023-07-31T14:43:10Z</dc:date>
    <item>
      <title>selection criteria for alerts in API call to https://api.ca.prismacloud.io/v2/alert</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/selection-criteria-for-alerts-in-api-call-to-https-api-ca/m-p/550936#M990</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;I'm using a call to CSPM Prisma API&amp;nbsp;&lt;A href="https://api.ca.prismacloud.io/v2/alert" target="_blank"&gt;https://api.ca.prismacloud.io/v2/alert&lt;/A&gt;&amp;nbsp;to get changes happened to alerts withing specific time range. For that absolute timeRange filter is used in call parayers with specific stratTime and endTime values set as described in API documentation here&amp;nbsp;&lt;A href="https://pan.dev/prisma-cloud/api/cspm/post-alerts-v-2/" target="_blank"&gt;https://pan.dev/prisma-cloud/api/cspm/post-alerts-v-2/&lt;/A&gt;. In general, the call works and returns a list of alerts with details. But I discovered that all of the alerts I get in the result data set are in status 'open' unless the alert was both opened and closed (dismissed, resolved) within the specified timeRange. In case when the alert was opened before the timeRange and resolved within timeRange it is not included in the result set. Is it expected behavior? Can it be altered to get all alerts that changed the status within timeRange by some call parameters or alert configuration?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;Sergii&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 17:06:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/selection-criteria-for-alerts-in-api-call-to-https-api-ca/m-p/550936#M990</guid>
      <dc:creator>SIurenko</dc:creator>
      <dc:date>2023-07-25T17:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: selection criteria for alerts in API call to https://api.ca.prismacloud.io/v2/alert</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/selection-criteria-for-alerts-in-api-call-to-https-api-ca/m-p/551782#M997</link>
      <description>&lt;P&gt;Hi Sergii,&lt;/P&gt;
&lt;P&gt;At a first look, this sounds like the expected behavior, to us a "change" means going from {never opened,open} to {dismissed,snoozed,resolved} within a time interval.&lt;/P&gt;
&lt;P&gt;However, let me take a closer look, can you reply with an example of retrieved alerts that demonstrate the problem, together with the query parameters you used?&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 14:43:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/selection-criteria-for-alerts-in-api-call-to-https-api-ca/m-p/551782#M997</guid>
      <dc:creator>JNeytchev</dc:creator>
      <dc:date>2023-07-31T14:43:10Z</dc:date>
    </item>
  </channel>
</rss>

