<?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 relating AD logs with DHCP in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26452#M5111</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am trying to add a IP address hint to the Active Directory logs. I know it isn't completely reliable, but it is just to get a general ideal of the IP address the workstations had when they generate some events. Sometimes the IP is already included in the event, but most times it isn't.&lt;/P&gt;

&lt;P&gt;They way I am trying to implement it is by building a state table with a scheduled query:&lt;BR /&gt;
index="dhcp" (description="DNS Update Successful" OR description="Renew") | dedup hostname | outputcsv dhcpstatetable&lt;BR /&gt;
And then using a automatic lookup to add a probableip field to the AD events.&lt;/P&gt;

&lt;P&gt;I have the problema that the outputcsv writes the csv to /var/run which I can't use to create a lookup definition. &lt;/P&gt;

&lt;P&gt;Is there a better way to do this?&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2013 14:28:06 GMT</pubDate>
    <dc:creator>krugger</dc:creator>
    <dc:date>2013-05-07T14:28:06Z</dc:date>
    <item>
      <title>relating AD logs with DHCP</title>
      <link>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26452#M5111</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am trying to add a IP address hint to the Active Directory logs. I know it isn't completely reliable, but it is just to get a general ideal of the IP address the workstations had when they generate some events. Sometimes the IP is already included in the event, but most times it isn't.&lt;/P&gt;

&lt;P&gt;They way I am trying to implement it is by building a state table with a scheduled query:&lt;BR /&gt;
index="dhcp" (description="DNS Update Successful" OR description="Renew") | dedup hostname | outputcsv dhcpstatetable&lt;BR /&gt;
And then using a automatic lookup to add a probableip field to the AD events.&lt;/P&gt;

&lt;P&gt;I have the problema that the outputcsv writes the csv to /var/run which I can't use to create a lookup definition. &lt;/P&gt;

&lt;P&gt;Is there a better way to do this?&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2013 14:28:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26452#M5111</guid>
      <dc:creator>krugger</dc:creator>
      <dc:date>2013-05-07T14:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: relating AD logs with DHCP</title>
      <link>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26453#M5112</link>
      <description>&lt;P&gt;outputlookup seems to solve it&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2013 14:36:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26453#M5112</guid>
      <dc:creator>krugger</dc:creator>
      <dc:date>2013-05-07T14:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: relating AD logs with DHCP</title>
      <link>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26454#M5113</link>
      <description>&lt;P&gt;You can create an empty dummy lookup where you need it and then use the outputlookup command to populate it.&lt;/P&gt;

&lt;P&gt;There is an example in the documentation of the command: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Outputlookup"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Outputlookup&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2013 21:54:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/relating-AD-logs-with-DHCP/m-p/26454#M5113</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2013-05-07T21:54:19Z</dc:date>
    </item>
  </channel>
</rss>

