<?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: Scripting in metrics with Splunk? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317688#M59400</link>
    <description>&lt;P&gt;As @richgalloway said in hist comment, in 7.0.0, you can only send one &lt;CODE&gt;_value&lt;/CODE&gt; and one &lt;CODE&gt;measurement&lt;/CODE&gt; in each metric event, but theoretically you can have as many dimensions (columns/tags/fields) as you want.&lt;/P&gt;

&lt;P&gt;You could parse &lt;CODE&gt;top&lt;/CODE&gt; output and send each row separately with the same timestamp. Each column would be a dimension but you would need to determine what you are sending as the &lt;CODE&gt;_value&lt;/CODE&gt; field in this case. Not really sure what the point of this would be, but it is doable. &lt;/P&gt;</description>
    <pubDate>Thu, 19 Oct 2017 14:07:49 GMT</pubDate>
    <dc:creator>rjthibod</dc:creator>
    <dc:date>2017-10-19T14:07:49Z</dc:date>
    <item>
      <title>Scripting in metrics with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317686#M59398</link>
      <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;Still getting my head around metrics. I shameless stole this line of bash and setup metrics and it's working . UI was cool. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;echo "mydesktop.cpu.util:$intCount|c" | nc -w 1 -u myheavyforwarders.domain.com 8125
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;With this in mind how would I send more than one metric? Say I wanted all the output of TOP? Can you send more than one metric at a time? I understand these metric can have dimension, is that basically an array of values? &lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2017 23:05:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317686#M59398</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2017-10-18T23:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: Scripting in metrics with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317687#M59399</link>
      <description>&lt;P&gt;As I understand metrics, each "event" is a single value.  Dimensions describe the value - process ID, user running the process, etc.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2017 14:01:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317687#M59399</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-10-19T14:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: Scripting in metrics with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317688#M59400</link>
      <description>&lt;P&gt;As @richgalloway said in hist comment, in 7.0.0, you can only send one &lt;CODE&gt;_value&lt;/CODE&gt; and one &lt;CODE&gt;measurement&lt;/CODE&gt; in each metric event, but theoretically you can have as many dimensions (columns/tags/fields) as you want.&lt;/P&gt;

&lt;P&gt;You could parse &lt;CODE&gt;top&lt;/CODE&gt; output and send each row separately with the same timestamp. Each column would be a dimension but you would need to determine what you are sending as the &lt;CODE&gt;_value&lt;/CODE&gt; field in this case. Not really sure what the point of this would be, but it is doable. &lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2017 14:07:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Scripting-in-metrics-with-Splunk/m-p/317688#M59400</guid>
      <dc:creator>rjthibod</dc:creator>
      <dc:date>2017-10-19T14:07:49Z</dc:date>
    </item>
  </channel>
</rss>

