<?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: UFs don't parse data, but docs say splunktcp-ssl  is only for &amp;quot;parsed&amp;quot; data to indexers? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632425#M108335</link>
    <description>&lt;P&gt;Please submit feedback using the form at the bottom of the documentation page you are looking at. That creates a ticket for the doc team and we will follow up, thank you!&lt;/P&gt;</description>
    <pubDate>Mon, 27 Feb 2023 21:35:59 GMT</pubDate>
    <dc:creator>ChrisG</dc:creator>
    <dc:date>2023-02-27T21:35:59Z</dc:date>
    <item>
      <title>Why don't UFs parse data when docs say splunktcp-ssl  is only for "parsed" data to indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632376#M108330</link>
      <description>&lt;P&gt;According to the Splunk documentation on the attribute [splunktcp-ssl:&amp;lt;port&amp;gt;] it states that:&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;* Use this stanza type if you are receiving encrypted, parsed data from a forwarder."&lt;/P&gt;
&lt;P&gt;UFs cook, but do not 'parse' the data.&amp;nbsp; Thus, is this effective to send encrypted data from the UF to indexers?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2023 21:11:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632376#M108330</guid>
      <dc:creator>dokaas_2</dc:creator>
      <dc:date>2023-02-27T21:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: UFs don't parse data, but docs say splunktcp-ssl  is only for "parsed" data to indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632418#M108334</link>
      <description>&lt;P&gt;I think this may be a place where the documentation needs improvement.&amp;nbsp; Splunk Cloud uses SSL exclusively with UFs so you should be able to, also.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2023 20:52:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632418#M108334</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-02-27T20:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: UFs don't parse data, but docs say splunktcp-ssl  is only for "parsed" data to indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632425#M108335</link>
      <description>&lt;P&gt;Please submit feedback using the form at the bottom of the documentation page you are looking at. That creates a ticket for the doc team and we will follow up, thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2023 21:35:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-don-t-UFs-parse-data-when-docs-say-splunktcp-ssl-is-only-for/m-p/632425#M108335</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2023-02-27T21:35:59Z</dc:date>
    </item>
  </channel>
</rss>

