<?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: response time in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51520#M22248</link>
    <description>&lt;P&gt;Kristian,&lt;/P&gt;

&lt;P&gt;It works, but this gives cumulative answer. Is it possible to get it per day? &lt;/P&gt;

&lt;P&gt;Thanks for your help&lt;BR /&gt;
Kalpesh&lt;/P&gt;</description>
    <pubDate>Tue, 15 May 2012 04:31:33 GMT</pubDate>
    <dc:creator>kunadkat</dc:creator>
    <dc:date>2012-05-15T04:31:33Z</dc:date>
    <item>
      <title>response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51516#M22244</link>
      <description>&lt;P&gt;I would like to put response time in three buckets. low &amp;lt; 1 second, medium &amp;lt; 2 second, high &amp;gt; 2 second. I would like to calculate % response time in low medium and high buckets. &lt;/P&gt;

&lt;P&gt;The following is the query:&lt;/P&gt;

&lt;P&gt;sourcetype="jboss" TOTAL SEARCH  TIME CAREWEB | eventstats count as total |eval rp=EASYDOC_JBOSS_TIME/1000 |  rangemap field=rp low=0-1.0 medium=1-2 high=2-100 | stats count by range&lt;/P&gt;

&lt;P&gt;Eventhough I see total in the fields, I am not able to use it in the eval to calculate %&lt;/P&gt;

&lt;P&gt;as per SLA I have to have produce a graph that shows that 99% of responsetime is less than 1 second&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:49:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51516#M22244</guid>
      <dc:creator>kunadkat</dc:creator>
      <dc:date>2020-09-28T11:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51517#M22245</link>
      <description>&lt;P&gt;You could try;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="jboss" TOTAL SEARCH TIME CAREWEB 
| eval rp=EASYDOC_JBOSS_TIME/1000 
| rangemap field=rp low=0-1.0 medium=1-2 high=2-100 
| stats c AS TOTAL c(eval(range="low")) AS OK_COUNT c(eval(range="medium")) AS NOT_OK_COUNT c(eval(range="high")) AS REALLY_BAD_COUNT 
| eval SLA_OK_PERC = round((OK_COUNT / TOTAL *100),2) 
| eval SLA_BAD_PERC = round((NOT_OK_COUNT / TOTAL * 100), 2) 
| eval SLA_DISASTER_PERC = round((REALLY_BAD_COUNT / TOTAL *100),2)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;HR /&gt;

&lt;P&gt;I believe that changing '&lt;CODE&gt;stats&lt;/CODE&gt;' for '&lt;CODE&gt;timechart span=1d&lt;/CODE&gt;' will give you the results you want - see below. I haven't tried it though, as I have no good sample logs available.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="jboss" TOTAL SEARCH TIME CAREWEB 
| eval rp=EASYDOC_JBOSS_TIME/1000 
| rangemap field=rp low=0-1.0 medium=1-2 high=2-100 
| timechart span=1d c AS TOTAL c(eval(range="low")) AS OK_COUNT c(eval(range="medium")) AS NOT_OK_COUNT c(eval(range="high")) AS REALLY_BAD_COUNT 
| eval SLA_OK_PERC = round((OK_COUNT / TOTAL *100),2) 
| eval SLA_BAD_PERC = round((NOT_OK_COUNT / TOTAL * 100), 2) 
| eval SLA_DISASTER_PERC = round((REALLY_BAD_COUNT / TOTAL *100),2)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 20:53:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51517#M22245</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-05-14T20:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51518#M22246</link>
      <description>&lt;P&gt;There is also the &lt;CODE&gt;percXX&lt;/CODE&gt; stats functions which compute the &lt;CODE&gt;XXth&lt;/CODE&gt; percentile of a data set.  This may (or equally may not) be a better approach to your measurement.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="jboss" TOTAL SEARCH TIME CAREWEB 
| eval rp=EASYDOC_JBOSS_TIME/1000 
| timechart perc99(rp)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 14 May 2012 23:22:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51518#M22246</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-05-14T23:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51519#M22247</link>
      <description>&lt;P&gt;Kristian, &lt;/P&gt;

&lt;P&gt;sourcetype="jboss" TOTAL SEARCH TIME CAREWEB &lt;BR /&gt;
| eval rp=EASYDOC_JBOSS_TIME/1000 &lt;BR /&gt;
| rangemap field=rp low=0-1.0 medium=1-2 high=2-100 &lt;BR /&gt;
| stats c AS TOTAL c(eval(range="low")) AS OK_COUNT c(eval(range="medium")) AS NOT_OK_COUNT c(eval(range="high")) AS REALLY_BAD_COUNT &lt;BR /&gt;
| eval SLA_OK_PERC = round((OK_COUNT / TOTAL *100),2) &lt;BR /&gt;
| eval SLA_BAD_PERC = round((NOT_OK_COUNT / TOTAL * 100), 2) &lt;BR /&gt;
| eval SLA_DISASTER_PERC = round((REALLY_BAD_COUNT / TOTAL *100),2)&lt;/P&gt;

&lt;P&gt;This works but how do I get this stats per day? &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:49:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51519#M22247</guid>
      <dc:creator>kunadkat</dc:creator>
      <dc:date>2020-09-28T11:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51520#M22248</link>
      <description>&lt;P&gt;Kristian,&lt;/P&gt;

&lt;P&gt;It works, but this gives cumulative answer. Is it possible to get it per day? &lt;/P&gt;

&lt;P&gt;Thanks for your help&lt;BR /&gt;
Kalpesh&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2012 04:31:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51520#M22248</guid>
      <dc:creator>kunadkat</dc:creator>
      <dc:date>2012-05-15T04:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51521#M22249</link>
      <description>&lt;P&gt;see update above. &lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2012 15:06:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51521#M22249</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-05-15T15:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51522#M22250</link>
      <description>&lt;P&gt;Worked. Thanks you very much&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2012 13:43:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51522#M22250</guid>
      <dc:creator>kunadkat</dc:creator>
      <dc:date>2012-05-18T13:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: response time</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51523#M22251</link>
      <description>&lt;P&gt;Feel free to mark the question as answered. /k&lt;/P&gt;</description>
      <pubDate>Mon, 21 May 2012 09:03:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/response-time/m-p/51523#M22251</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-05-21T09:03:19Z</dc:date>
    </item>
  </channel>
</rss>

