<?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 CMX automated data export in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/cmx-automated-data-export/m-p/3859894#M2482</link>
    <description>&lt;P&gt;We have a new instance of CMX (10.6) set up on our network, and are wanting to export the data into our Business Intelligence platform for longer term storage. We are only intending to do a daily export.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, the API for exporting large datasets from the Cassandra database doesn’t work, as per the bug report below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://quickview.cloudapps.cisco.com/quickview/bug/CSCvo15147" target="_blank"&gt;https://quickview.cloudapps.cisco.com/quickview/bug/CSCvo15147&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The recommended workaround is to use the “all client history” API. While this API does work, it does not page, and truncates at 5000 records. This means we are having to call the API every few minutes, and code a loop to continue calling it in small time increments until we get fewer than 5000 records. This is far from ideal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a work around to that work around, we are looking to create our own custom API. As per the documentation here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/CMX-Engage/API-docs/CMX-Engage-data-export.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/CMX-Engage/API-docs/CMX-Engage-data-export.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the documentation says to contact support, when we did so, we were told to post here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help anyone could provide would be greatly appreciated!&lt;/P&gt;</description>
    <pubDate>Tue, 21 May 2019 07:20:45 GMT</pubDate>
    <dc:creator>Scott O'Brien</dc:creator>
    <dc:date>2019-05-21T07:20:45Z</dc:date>
    <item>
      <title>CMX automated data export</title>
      <link>https://community.cisco.com/t5/controllers/cmx-automated-data-export/m-p/3859894#M2482</link>
      <description>&lt;P&gt;We have a new instance of CMX (10.6) set up on our network, and are wanting to export the data into our Business Intelligence platform for longer term storage. We are only intending to do a daily export.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, the API for exporting large datasets from the Cassandra database doesn’t work, as per the bug report below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://quickview.cloudapps.cisco.com/quickview/bug/CSCvo15147" target="_blank"&gt;https://quickview.cloudapps.cisco.com/quickview/bug/CSCvo15147&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The recommended workaround is to use the “all client history” API. While this API does work, it does not page, and truncates at 5000 records. This means we are having to call the API every few minutes, and code a loop to continue calling it in small time increments until we get fewer than 5000 records. This is far from ideal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a work around to that work around, we are looking to create our own custom API. As per the documentation here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/CMX-Engage/API-docs/CMX-Engage-data-export.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Mobility/CMX-Engage/API-docs/CMX-Engage-data-export.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the documentation says to contact support, when we did so, we were told to post here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help anyone could provide would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2019 07:20:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/cmx-automated-data-export/m-p/3859894#M2482</guid>
      <dc:creator>Scott O'Brien</dc:creator>
      <dc:date>2019-05-21T07:20:45Z</dc:date>
    </item>
    <item>
      <title>Re: CMX automated data export</title>
      <link>https://community.cisco.com/t5/controllers/cmx-automated-data-export/m-p/4630904#M2483</link>
      <description>&lt;P&gt;Known fixed releases beginning with&amp;nbsp;&lt;SPAN&gt;10.6(3.70) - according to the bug report linked above&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2022 16:33:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/cmx-automated-data-export/m-p/4630904#M2483</guid>
      <dc:creator>Alexander Stevenson</dc:creator>
      <dc:date>2022-06-13T16:33:27Z</dc:date>
    </item>
  </channel>
</rss>

