<?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 extracted field propagation across related events in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156441#M44020</link>
    <description>&lt;P&gt;Hey all,&lt;BR /&gt;
I have a event log that i have to generate reports off of for the BI team where i work. the problem i keep running into is that the different event types log different set of information all tied to a unique event_id, but i need to have one field of a specific event type tied to all the other events with the same id.&lt;/P&gt;

&lt;P&gt;example:&lt;BR /&gt;
time              event_id       Node             user         status              event_type&lt;BR /&gt;
18534564.56       05178          HIL-DEV01                     not_reporting       alert&lt;BR /&gt;
18640234.9        05179          ROV-HOST01                    disk_space_low      alert&lt;BR /&gt;
19538754.13       05178                           Hal9001                          closed&lt;/P&gt;

&lt;P&gt;in this example i want to assign node HIL-DEV01 across all events with the ID of 05178. I have tried to do this with transactions, but i have found that i lose unique time values for events inside the transaction.&lt;/P&gt;

&lt;P&gt;is it possible to do this with eval? or does anyone have an idea of what to do? if you need more info just let me know.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 17:10:27 GMT</pubDate>
    <dc:creator>twistedsixty4</dc:creator>
    <dc:date>2020-09-28T17:10:27Z</dc:date>
    <item>
      <title>extracted field propagation across related events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156441#M44020</link>
      <description>&lt;P&gt;Hey all,&lt;BR /&gt;
I have a event log that i have to generate reports off of for the BI team where i work. the problem i keep running into is that the different event types log different set of information all tied to a unique event_id, but i need to have one field of a specific event type tied to all the other events with the same id.&lt;/P&gt;

&lt;P&gt;example:&lt;BR /&gt;
time              event_id       Node             user         status              event_type&lt;BR /&gt;
18534564.56       05178          HIL-DEV01                     not_reporting       alert&lt;BR /&gt;
18640234.9        05179          ROV-HOST01                    disk_space_low      alert&lt;BR /&gt;
19538754.13       05178                           Hal9001                          closed&lt;/P&gt;

&lt;P&gt;in this example i want to assign node HIL-DEV01 across all events with the ID of 05178. I have tried to do this with transactions, but i have found that i lose unique time values for events inside the transaction.&lt;/P&gt;

&lt;P&gt;is it possible to do this with eval? or does anyone have an idea of what to do? if you need more info just let me know.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:10:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156441#M44020</guid>
      <dc:creator>twistedsixty4</dc:creator>
      <dc:date>2020-09-28T17:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: extracted field propagation across related events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156442#M44021</link>
      <description>&lt;P&gt;Try this and see if this is hat you need&lt;/P&gt;

&lt;P&gt;Some Search Terms | stats values(time) as Timers first(Node) as Node values(status) as Statuses values(event_type) as Events by event_id&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:10:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156442#M44021</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2020-09-28T17:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: extracted field propagation across related events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156443#M44022</link>
      <description>&lt;P&gt;Give this a try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;your base search | eventstats first(Node) as Node by event_id 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 24 Jul 2014 18:57:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156443#M44022</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-07-24T18:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: extracted field propagation across related events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156444#M44023</link>
      <description>&lt;P&gt;you are a godsend sir, this worked great!&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jul 2014 20:52:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/extracted-field-propagation-across-related-events/m-p/156444#M44023</guid>
      <dc:creator>twistedsixty4</dc:creator>
      <dc:date>2014-07-24T20:52:00Z</dc:date>
    </item>
  </channel>
</rss>

