<?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: Fuzzy time range searches and sub-searches. in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Fuzzy-time-range-searches-and-sub-searches/m-p/69294#M17387</link>
    <description>&lt;P&gt;It sounds very much like you could benefit from using the &lt;CODE&gt;localize&lt;/CODE&gt; command. The docs explain the concept pretty well so I'll just link you there: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Localize"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Localize&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jun 2012 04:55:46 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2012-06-07T04:55:46Z</dc:date>
    <item>
      <title>Fuzzy time range searches and sub-searches.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Fuzzy-time-range-searches-and-sub-searches/m-p/69293#M17386</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Looking for tips/hints on the best way to extract a value from a sub-search, including the timestamp that the is associated with the value, and perform a search in another index for that value within a fuzzy-ish range around that same timestamp.&lt;/P&gt;

&lt;P&gt;Scenario is this:&lt;BR /&gt;&lt;BR /&gt;
index foo has an IP address and a time and date.&lt;BR /&gt;
index bar ALSO has IP address, time and date, but contains additional values, such as OS&lt;/P&gt;

&lt;P&gt;In meta-search syntax, I'd like to do:&lt;/P&gt;

&lt;P&gt;index=bar fuzzyrange=2hr [ search index=foo ip=1.2.3.4 | return ip,timestamp ] &lt;/P&gt;

&lt;P&gt;And I'd like Splunk to magically take the timestamp from the subsearch and look for the same IP in the bar index, but with a two hour variation on that timestamp.&lt;/P&gt;

&lt;P&gt;Is there an easy way?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2012 00:44:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Fuzzy-time-range-searches-and-sub-searches/m-p/69293#M17386</guid>
      <dc:creator>howyagoin</dc:creator>
      <dc:date>2012-06-07T00:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: Fuzzy time range searches and sub-searches.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Fuzzy-time-range-searches-and-sub-searches/m-p/69294#M17387</link>
      <description>&lt;P&gt;It sounds very much like you could benefit from using the &lt;CODE&gt;localize&lt;/CODE&gt; command. The docs explain the concept pretty well so I'll just link you there: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Localize"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Localize&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2012 04:55:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Fuzzy-time-range-searches-and-sub-searches/m-p/69294#M17387</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-06-07T04:55:46Z</dc:date>
    </item>
  </channel>
</rss>

