<?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: Future Splunk Release Features - Wishlist in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Future-Splunk-Release-Features-Wishlist/m-p/374137#M166388</link>
    <description>&lt;P&gt;Few of the features I'm looking for&lt;BR /&gt;
1. Reduce SH clustering complexity. I like the concept of ElasticSearch whereby the objects are stored in data layer (not at Search layer)&lt;BR /&gt;
2. Removing password encryption using another technique rather than at time of restart. Currently it is a pain to orchestrate as the orchestration systems think the config files have changed as the checksums are different once Splunk restarts&lt;BR /&gt;
3. Hop entries in _internal data =&amp;gt; if a Univeral forwarder sends to another UF to another UF to Indexer, if there is a flag to identify the hops it went through.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Aug 2017 08:28:53 GMT</pubDate>
    <dc:creator>koshyk</dc:creator>
    <dc:date>2017-08-21T08:28:53Z</dc:date>
    <item>
      <title>Future Splunk Release Features - Wishlist</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Future-Splunk-Release-Features-Wishlist/m-p/374136#M166387</link>
      <description>&lt;P&gt;Since it is almost 4 years from Splunk6, there might be chance of Splunk7 this year?? &lt;BR /&gt;
Is there any official case management or feature wishlist option where we can put features that are required?&lt;/P&gt;

&lt;P&gt;(or let's use this thread in case if Splunk architects can see &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;   for future releases)&lt;/P&gt;</description>
      <pubDate>Mon, 21 Aug 2017 08:23:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Future-Splunk-Release-Features-Wishlist/m-p/374136#M166387</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2017-08-21T08:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: Future Splunk Release Features - Wishlist</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Future-Splunk-Release-Features-Wishlist/m-p/374137#M166388</link>
      <description>&lt;P&gt;Few of the features I'm looking for&lt;BR /&gt;
1. Reduce SH clustering complexity. I like the concept of ElasticSearch whereby the objects are stored in data layer (not at Search layer)&lt;BR /&gt;
2. Removing password encryption using another technique rather than at time of restart. Currently it is a pain to orchestrate as the orchestration systems think the config files have changed as the checksums are different once Splunk restarts&lt;BR /&gt;
3. Hop entries in _internal data =&amp;gt; if a Univeral forwarder sends to another UF to another UF to Indexer, if there is a flag to identify the hops it went through.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Aug 2017 08:28:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Future-Splunk-Release-Features-Wishlist/m-p/374137#M166388</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2017-08-21T08:28:53Z</dc:date>
    </item>
  </channel>
</rss>

