<?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 Software versioning format in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20896#M743</link>
    <description>&lt;P&gt;hello guys,&lt;/P&gt;

&lt;P&gt;i am trying to build a view of our software versions that we have deployed across our customer base.&lt;BR /&gt;
our software versioning follows the version, major, minor format, i.e.&lt;BR /&gt;
2.0.5&lt;/P&gt;

&lt;P&gt;i am trying to apply a range map to a single button on the view, but not only does range map not support decimal values, but these values are not 'valid' decimal numbers since they have two decimal points.&lt;/P&gt;

&lt;P&gt;does anyone know of a method to convert 2.0.5 to a number value we can run a calculation against.&lt;/P&gt;

&lt;P&gt;logically something like this could work.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;eval part1=left(version,3) - [returns 2.0]

part2 = tonumber(part1) * 100 - [returns 200]

part3 = right(version,1) - [returns 5]

part4 = part2 + tonumber(part3) - [returns 205]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;this seems like an overly complex method, does anyone have any suggestions on a cleaner way of doing this?&lt;BR /&gt;
is this even possible?&lt;/P&gt;</description>
    <pubDate>Tue, 22 Nov 2011 17:25:55 GMT</pubDate>
    <dc:creator>nickhills</dc:creator>
    <dc:date>2011-11-22T17:25:55Z</dc:date>
    <item>
      <title>Software versioning format</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20896#M743</link>
      <description>&lt;P&gt;hello guys,&lt;/P&gt;

&lt;P&gt;i am trying to build a view of our software versions that we have deployed across our customer base.&lt;BR /&gt;
our software versioning follows the version, major, minor format, i.e.&lt;BR /&gt;
2.0.5&lt;/P&gt;

&lt;P&gt;i am trying to apply a range map to a single button on the view, but not only does range map not support decimal values, but these values are not 'valid' decimal numbers since they have two decimal points.&lt;/P&gt;

&lt;P&gt;does anyone know of a method to convert 2.0.5 to a number value we can run a calculation against.&lt;/P&gt;

&lt;P&gt;logically something like this could work.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;eval part1=left(version,3) - [returns 2.0]

part2 = tonumber(part1) * 100 - [returns 200]

part3 = right(version,1) - [returns 5]

part4 = part2 + tonumber(part3) - [returns 205]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;this seems like an overly complex method, does anyone have any suggestions on a cleaner way of doing this?&lt;BR /&gt;
is this even possible?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2011 17:25:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20896#M743</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2011-11-22T17:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: Software versioning format</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20897#M744</link>
      <description>&lt;P&gt;See if this helps:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&amp;lt;my search&amp;gt; | rex field=version mode=sed "s/\.//g"&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;This will remove all dots from the field called &lt;CODE&gt;version&lt;/CODE&gt; and convert it to a number.&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;&amp;gt; please upvote and accept answer if you find it useful - thanks!&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2011 17:51:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20897#M744</guid>
      <dc:creator>_d_</dc:creator>
      <dc:date>2011-11-22T17:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Software versioning format</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20898#M745</link>
      <description>&lt;P&gt;perfect.&lt;/P&gt;

&lt;P&gt;i knew there would be a simple answer, i spent so much time trying to convert it to a numeric value, i didn't even think of regex.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2011 21:31:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/20898#M745</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2011-11-22T21:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: Software versioning format</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/539597#M36952</link>
      <description>&lt;P&gt;This drove me nuts for weeks until I found your solution.&amp;nbsp; Thank you very much!&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 23:56:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Software-versioning-format/m-p/539597#M36952</guid>
      <dc:creator>aferone</dc:creator>
      <dc:date>2021-02-11T23:56:34Z</dc:date>
    </item>
  </channel>
</rss>

