<?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: Help Joining Indexes in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120413#M32351</link>
    <description>&lt;P&gt;Well, &lt;CODE&gt;transaction&lt;/CODE&gt; has other problems and it's performance can easily be worse than &lt;CODE&gt;join&lt;/CODE&gt; but if your times are close together and you are using only 1 field that all events contain, it should be fine (e.g. your first &lt;CODE&gt;transaction&lt;/CODE&gt;) but I would be concerned about your second one on large data sets.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jul 2015 23:36:02 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-07-13T23:36:02Z</dc:date>
    <item>
      <title>Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120408#M32346</link>
      <description>&lt;P&gt;I have 2 indexes with a common field that I extracted (The JSession ID)&lt;/P&gt;

&lt;P&gt;So I want to join &lt;CODE&gt;index=main&lt;/CODE&gt;and &lt;CODE&gt;index=access&lt;/CODE&gt;by using the field RTG_JSession&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;index=access&lt;/CODE&gt; has web requests with the Jsession ID &lt;BR /&gt;
&lt;CODE&gt;index=main&lt;/CODE&gt; has the IP address with the Jsession ID &lt;/P&gt;

&lt;P&gt;So I want to have a table which shows the:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   IP Address | Web Request | JSession ID 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Here's my current search which could use some tweeking.. The RTG_IP field was extratced to grab the IP Address &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=main | Join RTG_JSession [search index=access | stats count by RTG_IP]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Jul 2015 16:06:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120408#M32346</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2015-07-13T16:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120409#M32347</link>
      <description>&lt;P&gt;Try to avoid &lt;CODE&gt;join&lt;/CODE&gt; ( &lt;CODE&gt;subsearches&lt;/CODE&gt; ) if you can.  Will this work?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=main OR index=access | stats values(*) AS * BY RTG_JSession | stats count AS "Web Requests" values(RTG_JSession) AS "JSession IDs" dc(RTG_JSession) AS "JSession ID count" BY RTG_IP | rename RTG_IP AS "IP Address"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Jul 2015 16:17:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120409#M32347</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-07-13T16:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120410#M32348</link>
      <description>&lt;P&gt;This was very close to what I needed. It seems to be that the 'Web Requests' field is counting the number of JSession's. I need to have 3 columns showing &lt;CODE&gt;IP Address | Web Requests | JSession ID&lt;/CODE&gt;.. The web requests are the HTTP calls we get, so "GET /browse/financeInquiry.jsp?provider=GE&amp;amp;_requestid=32423423423 HTTP/1.1" would be the Web Request. So I went ahead and extracted another field called RTG_WebReq which grabs these values. I also expect an IP Address to have many Jsessions and Web Requests &lt;/P&gt;

&lt;P&gt;Here's an example of what I'm looking for &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;172.20.197.82 | GET /browse/financeInquiry.jsp?provider=GE&amp;amp;_requestid=43534534 HTTP/1.1 | 99CA349F0BB69E402A678345AC007E2Z
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:40:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120410#M32348</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2020-09-29T06:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120411#M32349</link>
      <description>&lt;P&gt;OK, then, this should do it:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=main OR index=access | stats values(*) AS * BY RTG_JSession | stats count(RTG_WebReq) AS "Web Requests" values(RTG_JSession) AS "JSession IDs" dc(RTG_JSession) AS "JSession ID count" BY RTG_IP | rename RTG_IP AS "IP Address"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Jul 2015 18:28:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120411#M32349</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-07-13T18:28:04Z</dc:date>
    </item>
    <item>
      <title>Re: Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120412#M32350</link>
      <description>&lt;P&gt;I took a different approach and this does the trick. You gave me the idea to abandon the join which I now see why. Below is the search I used for anyone needing help in the future. Thanks for the help! &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=access OR Index=main | transaction RTG_JSession | transaction RTG_JSession RTG_IP RTG_WebReq | table RTG_IP RTG_JSession RTG_WebReq
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Jul 2015 23:33:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120412#M32350</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2015-07-13T23:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help Joining Indexes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120413#M32351</link>
      <description>&lt;P&gt;Well, &lt;CODE&gt;transaction&lt;/CODE&gt; has other problems and it's performance can easily be worse than &lt;CODE&gt;join&lt;/CODE&gt; but if your times are close together and you are using only 1 field that all events contain, it should be fine (e.g. your first &lt;CODE&gt;transaction&lt;/CODE&gt;) but I would be concerned about your second one on large data sets.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 23:36:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-Joining-Indexes/m-p/120413#M32351</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-07-13T23:36:02Z</dc:date>
    </item>
  </channel>
</rss>

