<?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 Normalizing (feature scaling) a datapoint in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194303#M187288</link>
    <description>&lt;P&gt;I have a search and I would like to normalize a data point so that I can use it effectively in conjunction with other data points to determine performance impact.  In particular, I have a search that is essentially a &lt;CODE&gt;stats count as hits ... by requestUri&lt;/CODE&gt;  I need to know &lt;CODE&gt;min(hits)&lt;/CODE&gt; and &lt;CODE&gt;max(hits)&lt;/CODE&gt; in order to determine the normalized value, which I imagine would require preprocessing.  Is this possible?  See &lt;A href="https://en.wikipedia.org/wiki/Feature_scaling"&gt;https://en.wikipedia.org/wiki/Feature_scaling&lt;/A&gt; if you're wondering what I'm trying to accomplish.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Aug 2015 16:03:57 GMT</pubDate>
    <dc:creator>bgourlie</dc:creator>
    <dc:date>2015-08-26T16:03:57Z</dc:date>
    <item>
      <title>Normalizing (feature scaling) a datapoint</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194303#M187288</link>
      <description>&lt;P&gt;I have a search and I would like to normalize a data point so that I can use it effectively in conjunction with other data points to determine performance impact.  In particular, I have a search that is essentially a &lt;CODE&gt;stats count as hits ... by requestUri&lt;/CODE&gt;  I need to know &lt;CODE&gt;min(hits)&lt;/CODE&gt; and &lt;CODE&gt;max(hits)&lt;/CODE&gt; in order to determine the normalized value, which I imagine would require preprocessing.  Is this possible?  See &lt;A href="https://en.wikipedia.org/wiki/Feature_scaling"&gt;https://en.wikipedia.org/wiki/Feature_scaling&lt;/A&gt; if you're wondering what I'm trying to accomplish.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2015 16:03:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194303#M187288</guid>
      <dc:creator>bgourlie</dc:creator>
      <dc:date>2015-08-26T16:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Normalizing (feature scaling) a datapoint</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194304#M187289</link>
      <description>&lt;P&gt;Many times this is desirable because of too-broad a span of datapoint values to see on a chart.  If this is your motivation, have you tried changing your Y-Axis to "log" scale?  If you have to do it, you can pre-process using &lt;CODE&gt;eventstats&lt;/CODE&gt; like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | stats count as hits ... BY requestUri | eventstats min(hits) AS minHits max(hits) AS maxHits | eval hitsPrime=(hits-minHits)/(maxHits-minHits)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 27 Aug 2015 14:30:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194304#M187289</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-08-27T14:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Normalizing (feature scaling) a datapoint</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194305#M187290</link>
      <description>&lt;P&gt;This is exactly what I needed.  Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 27 Aug 2015 15:47:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Normalizing-feature-scaling-a-datapoint/m-p/194305#M187290</guid>
      <dc:creator>bgourlie</dc:creator>
      <dc:date>2015-08-27T15:47:11Z</dc:date>
    </item>
  </channel>
</rss>

