<?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 E-Series REST API collector coming soon.... or real, real soon in Data Infrastructure Insights</title>
    <link>https://community.netapp.com/t5/Data-Infrastructure-Insights/E-Series-REST-API-collector-coming-soon-or-real-real-soon/m-p/452751#M223</link>
    <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One of the engineering projects we have been working on is building a E-Series collector for CI that uses E-Series' REST API. This should be easier for us to implement enhancements in the future, but also allow easier troubleshooting for y'all in the field as TLS+HTTP is more easily understood versus the legacy API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are going to ship this in a few weeks, but I could patch a CI tenant to expose this new collector option today, if you would like. This will result in a new E-Series REST collector tile option for collector creation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From a functionality standpoint, the REST collector currently is ~105% of what you are accustomed to with the existing legacy API option - we have added a few minor enhancements like populating the "isEncrypted" boolean value as appropriate, and node utilization % as a performance counter is available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions you may have:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How do I get it early? I want to be in with the in-crowd!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;PM me here, or email ostiguy at netapp dot com, with your CI tenant URI.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How do I migrate to it?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Ensure you have a CI AU with HTTPS connectivity to the E-Series array. Create a new E-Series REST collector, and once it is successful, you can then remove the legacy collector&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Will I lose history if I follow the migration plan above?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Nope&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What is required?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Monitor/read only level credentials, and HTTPS connectivity to the array from a CI Acquisition Unit hosting the collector. You can populate the IP/hostname field with a comma delimited string - the collector ONLY needs to speak to one controller in the array, but if you populate this field with a comma delimited string, CI should intelligently attempt to speak to the second controller IF for whatever reason the first is inaccessible. Populating this field with only one IP/simple hostname/FQDN is also technically possible, but probably not a best practice for resiliency.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is the off-array installable E-Series REST API deployment supported?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;No - we are only targeting E-Series arrays with native REST API capabilities. We'd recommend continuing to use the legacy collector for any older arrays lacking native REST API capabilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 11:29:17 GMT</pubDate>
    <dc:creator>ostiguy</dc:creator>
    <dc:date>2025-06-04T11:29:17Z</dc:date>
    <item>
      <title>E-Series REST API collector coming soon.... or real, real soon</title>
      <link>https://community.netapp.com/t5/Data-Infrastructure-Insights/E-Series-REST-API-collector-coming-soon-or-real-real-soon/m-p/452751#M223</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One of the engineering projects we have been working on is building a E-Series collector for CI that uses E-Series' REST API. This should be easier for us to implement enhancements in the future, but also allow easier troubleshooting for y'all in the field as TLS+HTTP is more easily understood versus the legacy API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are going to ship this in a few weeks, but I could patch a CI tenant to expose this new collector option today, if you would like. This will result in a new E-Series REST collector tile option for collector creation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From a functionality standpoint, the REST collector currently is ~105% of what you are accustomed to with the existing legacy API option - we have added a few minor enhancements like populating the "isEncrypted" boolean value as appropriate, and node utilization % as a performance counter is available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions you may have:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How do I get it early? I want to be in with the in-crowd!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;PM me here, or email ostiguy at netapp dot com, with your CI tenant URI.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How do I migrate to it?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Ensure you have a CI AU with HTTPS connectivity to the E-Series array. Create a new E-Series REST collector, and once it is successful, you can then remove the legacy collector&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Will I lose history if I follow the migration plan above?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Nope&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What is required?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Monitor/read only level credentials, and HTTPS connectivity to the array from a CI Acquisition Unit hosting the collector. You can populate the IP/hostname field with a comma delimited string - the collector ONLY needs to speak to one controller in the array, but if you populate this field with a comma delimited string, CI should intelligently attempt to speak to the second controller IF for whatever reason the first is inaccessible. Populating this field with only one IP/simple hostname/FQDN is also technically possible, but probably not a best practice for resiliency.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is the off-array installable E-Series REST API deployment supported?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;No - we are only targeting E-Series arrays with native REST API capabilities. We'd recommend continuing to use the legacy collector for any older arrays lacking native REST API capabilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 11:29:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Infrastructure-Insights/E-Series-REST-API-collector-coming-soon-or-real-real-soon/m-p/452751#M223</guid>
      <dc:creator>ostiguy</dc:creator>
      <dc:date>2025-06-04T11:29:17Z</dc:date>
    </item>
  </channel>
</rss>

