<?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: Spreading transaction duration over spans in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18846#M2792</link>
    <description>&lt;P&gt;I believe that the timestamp of the transacation as a whole is set to the timestamp of first event that makes up a transaction. The properties like duration and eventcount, are created once for each transaction. Thus you get a peak at 4PM, and none after that.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Apr 2013 13:46:12 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2013-04-29T13:46:12Z</dc:date>
    <item>
      <title>Spreading transaction duration over spans</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18845#M2791</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
I have some data containing transactions that might take short (a couple of seconds) or very long (hours). I want to have a timechart that shows the duration of the transactions in spans of 15 minutes. I have the following:&lt;/P&gt;

&lt;P&gt;source="&amp;lt;source&amp;gt;" | transaction tr startswith="start" endswith="end" | timechart sum(duration) span=15m by tr&lt;/P&gt;

&lt;P&gt;This works nicely when the transaction is not longer than 15 minutes, but when the duration is e.g. 1 hour and started at 4 PM, I have a tall bar in the span from 4:00PM to 4:15PM and none in the following 3 spans. What I want is to have a bar of 15 minutes in the first span, 15 minutes in the seconds span (4:15PM to 4:30PM), etc.&lt;BR /&gt;
Is this possible?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;BR /&gt;
David &lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2013 13:32:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18845#M2791</guid>
      <dc:creator>davidjehoul</dc:creator>
      <dc:date>2013-04-29T13:32:43Z</dc:date>
    </item>
    <item>
      <title>Re: Spreading transaction duration over spans</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18846#M2792</link>
      <description>&lt;P&gt;I believe that the timestamp of the transacation as a whole is set to the timestamp of first event that makes up a transaction. The properties like duration and eventcount, are created once for each transaction. Thus you get a peak at 4PM, and none after that.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2013 13:46:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18846#M2792</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-04-29T13:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: Spreading transaction duration over spans</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18847#M2793</link>
      <description>&lt;P&gt;I already was afraid for that. So I understand that using the transaction command is not the way to go. Can it be done in another way? Using bucket, etc.?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2013 06:07:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18847#M2793</guid>
      <dc:creator>davidjehoul</dc:creator>
      <dc:date>2013-04-30T06:07:32Z</dc:date>
    </item>
    <item>
      <title>Re: Spreading transaction duration over spans</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18848#M2794</link>
      <description>&lt;P&gt;This may not be exactly what you're looking for, but if you just want to have an overview;&lt;/P&gt;

&lt;P&gt;... | bucket _time span=15m | dedup tr _time | timechart c span=15m by tr |&lt;/P&gt;

&lt;P&gt;Assumption is that the &lt;CODE&gt;tr&lt;/CODE&gt; transaction identifier can be used as such, without any startswith/endswith constraints. So now you'll have a '1' or '0' for each 15-minute block per transaction. So this will NOT measure the real duration of a transaction, it will just show whether parts of a transaction happened during a 15 min block. This can be visualised like below (although it seems a little buggy on my end). No drilldown and mouse-over on the legend is not reliable.&lt;/P&gt;

&lt;P&gt;Click on the little charting icon and then 'formatting options'&lt;BR /&gt;
ensure it's a column chart, &lt;BR /&gt;
multi-series mode = split, &lt;BR /&gt;
missing values = omit &lt;BR /&gt;
Goto Y-axis, and set the min value to 0.99 max value to 1.01&lt;/P&gt;

&lt;P&gt;This will be a rather ugly hack showing the presence of a transaction as (set of) block(s). There will be a small whitespace between connected columns, e.g. &lt;CODE&gt;--- --  -&lt;/CODE&gt; would indicate three transactions, the first is 45 minutes long, then a 15 min break, then a 30-min transaction, then a 30 min break, and finally a 15 min transaction.&lt;/P&gt;

&lt;P&gt;There is probably a simpler way of doing this. &lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2013 09:40:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Spreading-transaction-duration-over-spans/m-p/18848#M2794</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-04-30T09:40:22Z</dc:date>
    </item>
  </channel>
</rss>

