<?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: Why don't I see Splunk events for containers with Phantom-ingested emails? in Splunk SOAR</title>
    <link>https://community.splunk.com/t5/Splunk-SOAR/Why-don-t-I-see-Splunk-events-for-containers-with-Phantom/m-p/511482#M442</link>
    <description>&lt;P&gt;The json logged by Phantom break's Splunk's parsing. Early fields in the json will be available for you to search on, but later fields such as label and status won't be automatically extracted.&lt;/P&gt;&lt;P&gt;I think the raw_email field is the one that breaks things. Based on a quick test, a json linter had no problem with what phantom was sending Splunk, so the issue seems more with Splunk parsing the dta.&lt;/P&gt;&lt;P&gt;As a workaround - extract the relevant fields at search time (or define your own local props):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=phantom_container 
| rex "\x22label\x22: \x22(?&amp;lt;label&amp;gt;[^\x22]+)\x22" 
| rex "\x22status\x22: \x22(?&amp;lt;status&amp;gt;[^\x22]+)\x22" 
| search label!="servicenow-poll" status=new 
| eval _time = strptime(create_time,"%Y-%m-%dT%H:%M:%S") + 10*60*60 
| stats min(_time) as _time, values(label) as label by id 
| timechart span=10m count by label&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jul 2020 10:02:32 GMT</pubDate>
    <dc:creator>gf13579</dc:creator>
    <dc:date>2020-07-29T10:02:32Z</dc:date>
    <item>
      <title>Why don't I see Splunk events for containers with Phantom-ingested emails?</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/Why-don-t-I-see-Splunk-events-for-containers-with-Phantom/m-p/511480#M441</link>
      <description>&lt;P&gt;If I try to search phantom container events by label, status or several other fields, I don't see events relating to containers created by the email poll-based ingestion feature of Phantom.&lt;/P&gt;&lt;P&gt;Why don't they show up?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jul 2020 09:56:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/Why-don-t-I-see-Splunk-events-for-containers-with-Phantom/m-p/511480#M441</guid>
      <dc:creator>gf13579</dc:creator>
      <dc:date>2020-07-29T09:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: Why don't I see Splunk events for containers with Phantom-ingested emails?</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/Why-don-t-I-see-Splunk-events-for-containers-with-Phantom/m-p/511482#M442</link>
      <description>&lt;P&gt;The json logged by Phantom break's Splunk's parsing. Early fields in the json will be available for you to search on, but later fields such as label and status won't be automatically extracted.&lt;/P&gt;&lt;P&gt;I think the raw_email field is the one that breaks things. Based on a quick test, a json linter had no problem with what phantom was sending Splunk, so the issue seems more with Splunk parsing the dta.&lt;/P&gt;&lt;P&gt;As a workaround - extract the relevant fields at search time (or define your own local props):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=phantom_container 
| rex "\x22label\x22: \x22(?&amp;lt;label&amp;gt;[^\x22]+)\x22" 
| rex "\x22status\x22: \x22(?&amp;lt;status&amp;gt;[^\x22]+)\x22" 
| search label!="servicenow-poll" status=new 
| eval _time = strptime(create_time,"%Y-%m-%dT%H:%M:%S") + 10*60*60 
| stats min(_time) as _time, values(label) as label by id 
| timechart span=10m count by label&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jul 2020 10:02:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/Why-don-t-I-see-Splunk-events-for-containers-with-Phantom/m-p/511482#M442</guid>
      <dc:creator>gf13579</dc:creator>
      <dc:date>2020-07-29T10:02:32Z</dc:date>
    </item>
  </channel>
</rss>

