<?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: no formatting options when using fieldformat? in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514706#M34400</link>
    <description>&lt;P&gt;Once you applied the &lt;FONT face="courier new,courier"&gt;fieldformat&lt;/FONT&gt;, the numbers (which are always right-justified) became a string (which are left-justified).&lt;BR /&gt;Perhaps the &lt;FONT face="courier new,courier"&gt;printf&lt;/FONT&gt; function will help. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/ConversionFunctions" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/ConversionFunctions&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Aug 2020 13:57:42 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-08-18T13:57:42Z</dc:date>
    <item>
      <title>limited formatting options when using fieldformat?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514553#M34378</link>
      <description>&lt;P&gt;Is applying (retaining?) conditional numerical value-based field formatting &lt;STRONG&gt;after&lt;/STRONG&gt; applying &lt;FONT face="andale mono,times"&gt;fieldformat&lt;/FONT&gt;&amp;nbsp;that normalizes the values - an option? (It appears &lt;A href="https://community.splunk.com/t5/Archive/Keep-numbers-right-aligned-after-using-fieldformat/td-p/151219" target="_self"&gt;not&lt;/A&gt;?)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="no fieldformat: right-justfied as it should" style="width: 217px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10331i59769A20FF6CF0BD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Splunk FF - Screen Shot 2020-08-17 at 2.21.37 PM.png" alt="no fieldformat: right-justfied as it should" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;no fieldformat: right-justfied as it should&lt;/span&gt;&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="after fieldformat: left justified" style="width: 217px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10332iE11CBE4D33BB541C/image-size/large?v=v2&amp;amp;px=999" role="button" title="Splunk FF - Screen Shot 2020-08-17 at 2.21.04 PM.png" alt="after fieldformat: left justified" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;after fieldformat: left justified&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Hope it's clear why neither option is satisfactory: fields with&amp;nbsp;&lt;FONT face="andale mono,times"&gt;fieldformat&lt;/FONT&gt;&amp;nbsp;applied - are left justified and with no (numerical) value-based conditional formatting making it counter-intuitive and generally unreadable. Fields w/o&amp;nbsp;&lt;FONT face="andale mono,times"&gt;fieldformat&lt;/FONT&gt;: can quickly and irrevocably get unreadable as they can easily get into petabytes depending on the search timeframe and how busy the application has been.&lt;/P&gt;&lt;P&gt;For comparison, this is from a much younger competing product enabling auto formatting and normalizing data in ways that appear to be missing in Splunk:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Datadog - Screen Shot 2020-08-17 at 2.34.24 PM.png" style="width: 840px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10330i91ED70222258CDFE/image-size/large?v=v2&amp;amp;px=999" role="button" title="Datadog - Screen Shot 2020-08-17 at 2.34.24 PM.png" alt="Datadog - Screen Shot 2020-08-17 at 2.34.24 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 15:55:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514553#M34378</guid>
      <dc:creator>mitag</dc:creator>
      <dc:date>2020-08-18T15:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: no formatting options when using fieldformat?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514706#M34400</link>
      <description>&lt;P&gt;Once you applied the &lt;FONT face="courier new,courier"&gt;fieldformat&lt;/FONT&gt;, the numbers (which are always right-justified) became a string (which are left-justified).&lt;BR /&gt;Perhaps the &lt;FONT face="courier new,courier"&gt;printf&lt;/FONT&gt; function will help. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/ConversionFunctions" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/ConversionFunctions&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 13:57:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514706#M34400</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-08-18T13:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: no formatting options when using fieldformat?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514733#M34403</link>
      <description>&lt;P&gt;&lt;FONT face="courier new,courier"&gt;printf&lt;/FONT&gt;&amp;nbsp;can't right-justify a string, correct? So &lt;FONT face="courier new,courier"&gt;printf&lt;/FONT&gt; isn't applicable here?&lt;/P&gt;&lt;P&gt;(Sure,&amp;nbsp;&lt;FONT face="courier new,courier"&gt;tostring&lt;/FONT&gt;'s output&amp;nbsp;&lt;EM&gt;may&lt;/EM&gt;&amp;nbsp;stay right-justified - yet conditional color formatting? Gone.)&lt;/P&gt;&lt;P&gt;The use case in my question, to make both large and small numbers readable in the same table using unit prefixes (aka multipliers like "kilo", "mega", etc.)? Dead in the water. Yet arguably this is Splunk's #1 job: "make data &lt;EM&gt;actionable&lt;/EM&gt;" - which can't be done w/o making data &lt;EM&gt;readable&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;Splunk does a fairly decent job with conditional color formatting on numerals in a table - I don't see similar options in the competing product I mentioned in my OP.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="conditional color formatting for numerals in a table" style="width: 826px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/10350iE9EB8AAA30062AB4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Splunk - formatting options - Screen Shot 2020-08-17 at 5.00.00 PM.png" alt="conditional color formatting for numerals in a table" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;conditional color formatting for numerals in a table&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Yet losing those formatting options the moment I try to make those numerals readable beyond what's available in column formatting? Find it hard to fathom.&lt;/P&gt;&lt;P&gt;P.S. I get the part about formatting strings vs. numerals - it's all over Splunk Answers including in &lt;A href="https://community.splunk.com/t5/Archive/Keep-numbers-right-aligned-after-using-fieldformat/m-p/151221/highlight/true#M22509" target="_self"&gt;the answer I've linked to in my OP&lt;/A&gt;. Perhaps it's too much to ask for Splunk to do conditional formatting based on raw values rather than formatted ones. Yet at least give me an option to right-justify a string w/o going to a CSS? Better yet, add unit prefixes to conditional formatting options?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 16:32:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514733#M34403</guid>
      <dc:creator>mitag</dc:creator>
      <dc:date>2020-08-18T16:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: no formatting options when using fieldformat?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514769#M34405</link>
      <description>&lt;P&gt;I'm sure of all of printf's functionality.&amp;nbsp; I know it can left-justify and was hoping it could right-justify.&lt;/P&gt;&lt;P&gt;Consider making your suggestions at &lt;A href="https://ideas.splunk.com" target="_blank" rel="noopener"&gt;https://ideas.splunk.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 20:29:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/limited-formatting-options-when-using-fieldformat/m-p/514769#M34405</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-08-18T20:29:13Z</dc:date>
    </item>
  </channel>
</rss>

