<?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 Get the csv data into the metric_csv index in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Get-the-csv-data-into-the-metric-csv-index/m-p/389406#M100237</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;We have several CSV files with 300K lines, where I have a timestamp and the columns describing numeric KPIs, with header. &lt;BR /&gt;
We need to visualize it with annotations, which we basically managed. The first try was with the lookup, which was slow and the way of writing searches was a bit difficult. Then we uploaded the file into the index we have, which improved both the speed and made searching easier.&lt;BR /&gt;
Now, we would still wish a bit better performance. I came across of the metric index and metric_csv sourcetype.&lt;BR /&gt;
Would that be much faster than the normal index with the sourcetype="csv"?&lt;BR /&gt;
I mean showing like month of data (100K lines) on the line chart with 5 KPIs?&lt;/P&gt;

&lt;P&gt;And the main Question:&lt;BR /&gt;
- As per  the documentation there is a following format for the metric_csv required:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;"metric_timestamp","metric_name","_value","process_object_guid"
"1509997011","process.cpu.avg","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
"1509997011","process.cpu.min","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
"1509997011","process.cpu.max","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Which is basically not what we have. As mentioned, we have a header, the first column is a timestamp and then there are numeric KPIs in the next columns with the values in the rows. So, the above example would look as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; "metric_timestamp","process.cpu.avg","process.cpu.min","process.cpu.max"
 "1509997011","2563454144","2563454144","2563454144"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We do not have any "dimensions.&lt;BR /&gt;
Is there any way to read this form into the metric index?&lt;BR /&gt;
Or do we have to transfor all the csv files we have?&lt;BR /&gt;
And of course the question before, would the metric index be much faster in this case as the normal index with the sourcetype "csv", which we have at the moment? I mean, is it worth at all performance wise?&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;BR /&gt;
Kamil&lt;/P&gt;</description>
    <pubDate>Fri, 09 Nov 2018 09:11:01 GMT</pubDate>
    <dc:creator>damucka</dc:creator>
    <dc:date>2018-11-09T09:11:01Z</dc:date>
    <item>
      <title>Get the csv data into the metric_csv index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Get-the-csv-data-into-the-metric-csv-index/m-p/389406#M100237</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;We have several CSV files with 300K lines, where I have a timestamp and the columns describing numeric KPIs, with header. &lt;BR /&gt;
We need to visualize it with annotations, which we basically managed. The first try was with the lookup, which was slow and the way of writing searches was a bit difficult. Then we uploaded the file into the index we have, which improved both the speed and made searching easier.&lt;BR /&gt;
Now, we would still wish a bit better performance. I came across of the metric index and metric_csv sourcetype.&lt;BR /&gt;
Would that be much faster than the normal index with the sourcetype="csv"?&lt;BR /&gt;
I mean showing like month of data (100K lines) on the line chart with 5 KPIs?&lt;/P&gt;

&lt;P&gt;And the main Question:&lt;BR /&gt;
- As per  the documentation there is a following format for the metric_csv required:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;"metric_timestamp","metric_name","_value","process_object_guid"
"1509997011","process.cpu.avg","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
"1509997011","process.cpu.min","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
"1509997011","process.cpu.max","2563454144","dbd1414b-378e-48bd-9735-bc2bab1e58fa"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Which is basically not what we have. As mentioned, we have a header, the first column is a timestamp and then there are numeric KPIs in the next columns with the values in the rows. So, the above example would look as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; "metric_timestamp","process.cpu.avg","process.cpu.min","process.cpu.max"
 "1509997011","2563454144","2563454144","2563454144"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We do not have any "dimensions.&lt;BR /&gt;
Is there any way to read this form into the metric index?&lt;BR /&gt;
Or do we have to transfor all the csv files we have?&lt;BR /&gt;
And of course the question before, would the metric index be much faster in this case as the normal index with the sourcetype "csv", which we have at the moment? I mean, is it worth at all performance wise?&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;BR /&gt;
Kamil&lt;/P&gt;</description>
      <pubDate>Fri, 09 Nov 2018 09:11:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Get-the-csv-data-into-the-metric-csv-index/m-p/389406#M100237</guid>
      <dc:creator>damucka</dc:creator>
      <dc:date>2018-11-09T09:11:01Z</dc:date>
    </item>
  </channel>
</rss>

