<?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: Functions in splunk query language in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Functions-in-splunk-query-language/m-p/79547#M20140</link>
    <description>&lt;P&gt;Splunk's search language is extremely flexible.  There are a number of commands out-of-the-box such as "| eval" and "| transaction".  If you find something that can't be done using a shipped command, Splunk gives the ability to create your own search command using python.&lt;/P&gt;

&lt;P&gt;See: &lt;A href="http://www.splunk.com/base/Documentation/latest/SearchReference/WhatsInThisManual"&gt;Search Reference&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Apr 2011 18:52:12 GMT</pubDate>
    <dc:creator>hazekamp</dc:creator>
    <dc:date>2011-04-15T18:52:12Z</dc:date>
    <item>
      <title>Functions in splunk query language</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Functions-in-splunk-query-language/m-p/79546#M20139</link>
      <description>&lt;P&gt;Is it possible to create functions in the splunk query language? Right now I am working to try and correlate call detail records for a telephony platform. Essentially every call can generate N records, where N is determined by the type of call, features invoked, etc. To correlate the records correctly, it would be awesome if I could have some sort of branching ability based on the values of fields. Something along these lines:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;if(service_provider==wdv_trunking,(true search query),(false search query))?
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 12 Apr 2011 20:58:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Functions-in-splunk-query-language/m-p/79546#M20139</guid>
      <dc:creator>msarro</dc:creator>
      <dc:date>2011-04-12T20:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Functions in splunk query language</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Functions-in-splunk-query-language/m-p/79547#M20140</link>
      <description>&lt;P&gt;Splunk's search language is extremely flexible.  There are a number of commands out-of-the-box such as "| eval" and "| transaction".  If you find something that can't be done using a shipped command, Splunk gives the ability to create your own search command using python.&lt;/P&gt;

&lt;P&gt;See: &lt;A href="http://www.splunk.com/base/Documentation/latest/SearchReference/WhatsInThisManual"&gt;Search Reference&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2011 18:52:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Functions-in-splunk-query-language/m-p/79547#M20140</guid>
      <dc:creator>hazekamp</dc:creator>
      <dc:date>2011-04-15T18:52:12Z</dc:date>
    </item>
  </channel>
</rss>

