<?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 Splunk Could Not Get Description for Event in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Could-Not-Get-Description-for-Event/m-p/595663#M104040</link>
    <description>&lt;P&gt;I've seen this on some older posts, but I am currently battling this issue. For some hosts, restarting it makes the logs start flowing again without the above error message (Suggesting a delayed start is the answer). But on some of them, a restart does nothing, there is real security logs that Splunk is merely reporting above error message for.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Apr 2022 22:26:41 GMT</pubDate>
    <dc:creator>andrew_burnett</dc:creator>
    <dc:date>2022-04-27T22:26:41Z</dc:date>
    <item>
      <title>Splunk Could Not Get Description for Event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Could-Not-Get-Description-for-Event/m-p/595663#M104040</link>
      <description>&lt;P&gt;I've seen this on some older posts, but I am currently battling this issue. For some hosts, restarting it makes the logs start flowing again without the above error message (Suggesting a delayed start is the answer). But on some of them, a restart does nothing, there is real security logs that Splunk is merely reporting above error message for.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Apr 2022 22:26:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Could-Not-Get-Description-for-Event/m-p/595663#M104040</guid>
      <dc:creator>andrew_burnett</dc:creator>
      <dc:date>2022-04-27T22:26:41Z</dc:date>
    </item>
  </channel>
</rss>

