<?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: statement optimization because the link is the same for more condition. I like to use or operator in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/statement-optimization-because-the-link-is-the-same-for-more/m-p/435884#M191151</link>
    <description>&lt;P&gt;If you omit the &lt;CODE&gt;field="..."&lt;/CODE&gt; attribute then one condition will apply to all fields.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Aug 2019 15:55:29 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-08-08T15:55:29Z</dc:date>
    <item>
      <title>statement optimization because the link is the same for more condition. I like to use or operator</title>
      <link>https://community.splunk.com/t5/Splunk-Search/statement-optimization-because-the-link-is-the-same-for-more/m-p/435883#M191150</link>
      <description>&lt;P&gt;how can i optimize this statement :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;       &amp;lt;condition field="title"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
       &amp;lt;/condition&amp;gt;

       &amp;lt;condition field="Site"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="response"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="last_checked"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="response_time"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="average"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="range"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="sparkline_response_time"&amp;gt;
          &amp;lt;link&amp;gt;
            &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.title$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
          &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="Serveur"&amp;gt;
           &amp;lt;link&amp;gt;
              &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.Serveur$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
            &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;

        &amp;lt;condition field="packet_loss"&amp;gt;
           &amp;lt;link&amp;gt;
              &amp;lt;![CDATA[/app/website_monitoring/status_history?form.title=$row.Serveur$&amp;amp;earliest=$earliest$&amp;amp;latest=$latest$]]&amp;gt;
            &amp;lt;/link&amp;gt;
        &amp;lt;/condition&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 08 Aug 2019 14:12:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/statement-optimization-because-the-link-is-the-same-for-more/m-p/435883#M191150</guid>
      <dc:creator>w044f</dc:creator>
      <dc:date>2019-08-08T14:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: statement optimization because the link is the same for more condition. I like to use or operator</title>
      <link>https://community.splunk.com/t5/Splunk-Search/statement-optimization-because-the-link-is-the-same-for-more/m-p/435884#M191151</link>
      <description>&lt;P&gt;If you omit the &lt;CODE&gt;field="..."&lt;/CODE&gt; attribute then one condition will apply to all fields.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2019 15:55:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/statement-optimization-because-the-link-is-the-same-for-more/m-p/435884#M191151</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-08-08T15:55:29Z</dc:date>
    </item>
  </channel>
</rss>

