<?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: Why are eval fields not in table? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-are-eval-fields-not-in-table/m-p/599190#M208596</link>
    <description>&lt;P&gt;The problem is with the web-calls field name.&amp;nbsp; The &lt;FONT face="courier new,courier"&gt;eval&lt;/FONT&gt; command is computing percent as &lt;FONT face="courier new,courier"&gt;(web-(calls*100/totalweb))&lt;/FONT&gt;, but since the web and calls fields don't exist they can't be subtracted so the percent field can't be computed.&amp;nbsp; Percent is set to null and is displayed as an empty field.&amp;nbsp; This is why hyphens should not be used in field names.&amp;nbsp; If the hyphen can't be changed then surround the field name in single quotes ('web-calls') so Splunk knows it's a field rather than an expression.&lt;/P&gt;</description>
    <pubDate>Wed, 25 May 2022 00:24:30 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2022-05-25T00:24:30Z</dc:date>
    <item>
      <title>Why are eval fields not in table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-eval-fields-not-in-table/m-p/599169#M208592</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Iam trying a simple query where i want to see the percentage of calls with a particular response time in splunk and somehow the percent field is coming as empty in the table.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;index = xyz http_status=200 | stats count(request_ms) as web-calls by request_ms | eventstats sum(web-calls) as totalwb |eval percent=(web-calls*100/totalwb) | table request_ms web-calls totalwb percent&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 20:35:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-eval-fields-not-in-table/m-p/599169#M208592</guid>
      <dc:creator>Span</dc:creator>
      <dc:date>2022-05-24T20:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: Why are eval fields not in table?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-eval-fields-not-in-table/m-p/599190#M208596</link>
      <description>&lt;P&gt;The problem is with the web-calls field name.&amp;nbsp; The &lt;FONT face="courier new,courier"&gt;eval&lt;/FONT&gt; command is computing percent as &lt;FONT face="courier new,courier"&gt;(web-(calls*100/totalweb))&lt;/FONT&gt;, but since the web and calls fields don't exist they can't be subtracted so the percent field can't be computed.&amp;nbsp; Percent is set to null and is displayed as an empty field.&amp;nbsp; This is why hyphens should not be used in field names.&amp;nbsp; If the hyphen can't be changed then surround the field name in single quotes ('web-calls') so Splunk knows it's a field rather than an expression.&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2022 00:24:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-eval-fields-not-in-table/m-p/599190#M208596</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-05-25T00:24:30Z</dc:date>
    </item>
  </channel>
</rss>

