<?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: FMC Rest API hit count in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4533453#M376</link>
    <description>&lt;P&gt;I don't have a good setup for testing this but I found on my box when I had the curly braces around the device ID I saw the same problem you are hitting.&amp;nbsp; When I removed that I don't see the same error about device ID.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just did a filter like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;deviceId:7ed2e4e2-590e-11ec-83fb-86a1d0ba83f9&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see the design document had a similar example so I think the curly braces are more just to separate in the documentation but shouldn't be passed from what I can tell.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jan 2022 16:45:29 GMT</pubDate>
    <dc:creator>jarsmith</dc:creator>
    <dc:date>2022-01-18T16:45:29Z</dc:date>
    <item>
      <title>FMC Rest API hit count</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4520708#M370</link>
      <description>&lt;P&gt;Hi! I've been trying to get a REST API call to work with no luck, I wanted to get the hit counts for all rules in an ACP, I see that I need to give a Device ID but I've tried the FTD HA Pair ID, and just the devices ID and evertime I get device Id is invalid so I'm wondering if my ID is really wrong or if its a problem with the request.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the request I'm doing&lt;/P&gt;&lt;P&gt;Device ID&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"id": "210a246a-e468-11e8-bd5d-8ecb5cb2c3a9",&lt;BR /&gt;"type": "Device",&lt;BR /&gt;"links": {&lt;BR /&gt;"self": "https://x.x.x.x/api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/devices/devicerecords/210a246a-e468-11e8-bd5d-8ecb5cb2c3a9"&lt;BR /&gt;},&lt;BR /&gt;"name": xxxxx&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;REQUEST - https://x.x.x.x/api/fmc_config/v1/domain/global/policy/accesspolicies/780CF067-649A-0ed3-0000-042949674015/operational/hitcounts?filter="deviceId:&lt;/SPAN&gt;&lt;SPAN&gt;{d10e2c32-ffbe-11e8-9e90-9055102fe195&lt;/SPAN&gt;&lt;SPAN&gt;};fetchZeroHitCount:&lt;/SPAN&gt;&lt;SPAN&gt;{false&lt;/SPAN&gt;&lt;SPAN&gt;}"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For HA Pair&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"items": [&lt;BR /&gt;{&lt;BR /&gt;"id": "d10e2c32-ffbe-11e8-9e90-9055102fe195",&lt;BR /&gt;"type": "DeviceHAPair",&lt;BR /&gt;"links": {&lt;BR /&gt;"self": "https://x.x.x.x/api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/devicehapairs/ftddevicehapairs/d10e2c32-ffbe-11e8-9e90-9055102fe195"&lt;BR /&gt;},&lt;BR /&gt;"name": xxxxx&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;REQUEST - https://x.x.x.x/api/fmc_config/v1/domain/global/policy/accesspolicies/780CF067-649A-0ed3-0000-042949674015/operational/hitcounts?filter="deviceId:{d10e2c32-ffbe-11e8-9e90-9055102fe195};fetchZeroHitCount:{false}"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Got the same response using explorer&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"error"&lt;/SPAN&gt;&lt;SPAN&gt;:&amp;nbsp;{&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"category"&lt;/SPAN&gt;&lt;SPAN&gt;:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"FRAMEWORK"&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"messages"&lt;/SPAN&gt;&lt;SPAN&gt;:&amp;nbsp;[&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"description"&lt;/SPAN&gt;&lt;SPAN&gt;:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"deviceId&amp;nbsp;value&amp;nbsp;is&amp;nbsp;invalid."&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;],&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"severity"&lt;/SPAN&gt;&lt;SPAN&gt;:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;"ERROR"&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 17 Dec 2021 18:09:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4520708#M370</guid>
      <dc:creator>Luis Seyler</dc:creator>
      <dc:date>2021-12-17T18:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: FMC Rest API hit count</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4533453#M376</link>
      <description>&lt;P&gt;I don't have a good setup for testing this but I found on my box when I had the curly braces around the device ID I saw the same problem you are hitting.&amp;nbsp; When I removed that I don't see the same error about device ID.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just did a filter like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;deviceId:7ed2e4e2-590e-11ec-83fb-86a1d0ba83f9&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see the design document had a similar example so I think the curly braces are more just to separate in the documentation but shouldn't be passed from what I can tell.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 16:45:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4533453#M376</guid>
      <dc:creator>jarsmith</dc:creator>
      <dc:date>2022-01-18T16:45:29Z</dc:date>
    </item>
    <item>
      <title>Re: FMC Rest API hit count</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4533477#M377</link>
      <description>&lt;P&gt;That was it! Thank you so much! and it was so simple hahahaha&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 17:08:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-hit-count/m-p/4533477#M377</guid>
      <dc:creator>Luis Seyler</dc:creator>
      <dc:date>2022-01-18T17:08:45Z</dc:date>
    </item>
  </channel>
</rss>

