<?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: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122450#M32984</link>
    <description>&lt;P&gt;Consider going with a structured format such as JSON:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
  "timestamp": "...",
  "client_host": "...",
  "client_id": "...",
  "report_id": "...",
  "data": [
    {"domain": "...", "duration": 123},
    {"domain": "...", "duration": 456},
    ...
  ]
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Very easy to parse and work with afterwards, for any number of data points in a single event.&lt;/P&gt;

&lt;P&gt;As for your last question, please rephrase - I don't quite grasp what you're asking for.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Nov 2014 17:47:58 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-11-17T17:47:58Z</dc:date>
    <item>
      <title>How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122447#M32981</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;
I have the following logs:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;10/01/2014 00:00:00 -0500, client_host="172.24.1.41", client_id=db01, report_id=RAS04, igoogleinicio.com=3491,  webair.com=13148
10/01/2014 00:00:00 -0500, client_host="172.24.1.41", client_id=db01, report_id=RAS04, smtp.ec.pe=1313,  your-server.de=13148
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;These data need to view them as a table:   ... | table *&lt;BR /&gt;
And show me the header like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;client_host  |  client_id  |  report_id  |  igoogleinicio_com  |  webair_com  |  smtp_ec_br  |  your_server_de
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As you can see, the fields that have:   _  and  .  are replaced by   _  (underline).&lt;BR /&gt;
There will be no way around this?&lt;BR /&gt;
I thank You in advance.&lt;/P&gt;

&lt;P&gt;Regards&lt;BR /&gt;
Jorge&lt;/P&gt;</description>
      <pubDate>Sun, 16 Nov 2014 19:11:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122447#M32981</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2014-11-16T19:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122448#M32982</link>
      <description>&lt;P&gt;You could set up your own key-value extraction with &lt;CODE&gt;CLEAN_KEYS = false&lt;/CODE&gt;... however, that often gets you into trouble when using field names that have non-word characters in them. For example, running &lt;CODE&gt;... | eval foo = your-server.de&lt;/CODE&gt; will look for fields called &lt;CODE&gt;your&lt;/CODE&gt;, &lt;CODE&gt;server&lt;/CODE&gt;, and &lt;CODE&gt;de&lt;/CODE&gt; and perform subtraction resp. string concatenation on their values.&lt;/P&gt;

&lt;P&gt;I'd say the greater issue here is that you have values used as field names. Your events would be nicer to use if they looked like this: &lt;CODE&gt;... server=your-server.de duration=13148&lt;/CODE&gt;. Then you'd have no trouble with cleaned keys and an easy time building reports off the data generically without knowing the domains... which you need to if they're the field names.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Nov 2014 23:00:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122448#M32982</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-11-16T23:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122449#M32983</link>
      <description>&lt;P&gt;Thanks for the tip.&lt;BR /&gt;
I wish it were as comets, but those who come are dynamic fields, often reaching 10 to 20 "fields =" with different domain names.&lt;BR /&gt;
consultation, which would put the value CLEAN_KEYS&lt;BR /&gt;
Currently the SourceType is "report" and am configuring props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[report]
REPORT-rpt_1=no_clean_keys
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In transforms.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[no_clean_keys]
DELIMS       = ",", "="
CAN_OPTIMIZE = false
MV_ADD       = true
CLEAN_KEYS = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Extract the fields well, as needed. But keep the above fields, there will be way to clean?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 00:03:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122449#M32983</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2014-11-17T00:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122450#M32984</link>
      <description>&lt;P&gt;Consider going with a structured format such as JSON:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
  "timestamp": "...",
  "client_host": "...",
  "client_id": "...",
  "report_id": "...",
  "data": [
    {"domain": "...", "duration": 123},
    {"domain": "...", "duration": 456},
    ...
  ]
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Very easy to parse and work with afterwards, for any number of data points in a single event.&lt;/P&gt;

&lt;P&gt;As for your last question, please rephrase - I don't quite grasp what you're asking for.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 17:47:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122450#M32984</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-11-17T17:47:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122451#M32985</link>
      <description>&lt;P&gt;Hi Martin&lt;BR /&gt;
What is happening after setting the props and transforms, is showing me the above fields and new fields&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;client_host  |  client_id  |  report_id  |  igoogleinicio_com  | igoogleinicio.com  |  webair_com |  webair.com  |  smtp_ec_br  | smtp.ec.br  |  your_server_de |  your-server.de
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:07:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122451#M32985</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2014-11-17T18:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122452#M32986</link>
      <description>&lt;P&gt;The original key-value extractions are still active. Set &lt;CODE&gt;KV_MODE = none&lt;/CODE&gt; in props.conf to turn them off.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:14:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122452#M32986</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-11-17T18:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122453#M32987</link>
      <description>&lt;P&gt;Excellent @martin_mueller!!!&lt;BR /&gt;
I knew you could&lt;BR /&gt;
thank you very much&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:23:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122453#M32987</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2014-11-17T18:23:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122454#M32988</link>
      <description>&lt;P&gt;I still maintain that using varying domains as field names is going to end in tears...&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:24:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122454#M32988</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-11-17T18:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122455#M32989</link>
      <description>&lt;P&gt;Martin understand, this is for a report that is generated monthly with a "bucket"&lt;BR /&gt;
For example: Top 3 mailserver for day&lt;BR /&gt;
This is stored in a summary, and then it is called by some dashboards.&lt;BR /&gt;
Thankz&lt;/P&gt;

&lt;P&gt;Jorge&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:28:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122455#M32989</guid>
      <dc:creator>jrodriguezap</dc:creator>
      <dc:date>2014-11-17T18:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent field names with periods (.) OR  hyphens (-) from getting replaced with underscores (_)?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122456#M32990</link>
      <description>&lt;P&gt;How is that &lt;CODE&gt;top 3 mailserver&lt;/CODE&gt; supposed to work if your mailserver domains are the field names?&lt;/P&gt;

&lt;P&gt;...oh well, as long as it works for you &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2014 18:29:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-prevent-field-names-with-periods-OR-hyphens-from-getting/m-p/122456#M32990</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-11-17T18:29:48Z</dc:date>
    </item>
  </channel>
</rss>

