<?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: TIME_FORMAT and XML in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89683#M4893</link>
    <description>&lt;P&gt;Are you editing the correct props.conf? (i.e. where the parsing occurs).&lt;BR /&gt;
If you have a Universal Forwarder -&amp;gt; Indexer OR Lightweight Forwarder -&amp;gt; Indexer setup, the props.conf to edit is on the Indexer.&lt;/P&gt;

&lt;P&gt;If you are using a full/heavy forwarder, the settings should go there.&lt;/P&gt;

&lt;P&gt;Apart from that your settings look good. You could possibly further qualify your TIME_PREFIX regex with (if tour 'real' timestamps are the actually in the beginning of the line);&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;TIME_PREFIX=^\[&lt;/CODE&gt;  &lt;/P&gt;

&lt;P&gt;How have you configured linebreaking? I'd recommend that you use&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE=false
LINE_BREAKER = ([\r\n]+)\[\d\d
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which explicitly tells splunk to break events after a newline followed by the beginning of a 'real' timestamp.&lt;/P&gt;

&lt;P&gt;Hope this helps. If not, please give us more of your props.conf, and perhaps some more sample events.&lt;/P&gt;

&lt;P&gt;/Kristian&lt;/P&gt;</description>
    <pubDate>Mon, 12 Mar 2012 21:10:40 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2012-03-12T21:10:40Z</dc:date>
    <item>
      <title>TIME_FORMAT and XML</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89682#M4892</link>
      <description>&lt;P&gt;Howdy,&lt;/P&gt;

&lt;P&gt;I'm running in to a problem getting some XML to parse in to events properly. The log has multi-line entries as you might expect and in the XML are date strings that I want Splunk to ignore. So, each log entry begins with the following time stamp (which I want to use):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[03/12/12 16:15:30.103]: &amp;lt;Some log data goes here&amp;gt;
&amp;lt;possibly followed by a bunch of XML&amp;gt;
[03/12/12 16:15:30.112]: &amp;lt;Some more log data goes here&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The entries in the log file might only a single line long or might be as long as several hundred lines of XML before the next so-called real time spamp. Part of the XML data being generated are time strings like this: &lt;CODE&gt;20120312161445.247Z&lt;/CODE&gt;, which I don't want.&lt;/P&gt;

&lt;P&gt;What I want is for all of the lines between one time stamp and the next to be grouped in to a single event.&lt;/P&gt;

&lt;P&gt;Here's what I have in my props.conf file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = \[
TIME_FORMAT = %m/%d/%y %H:%M:%S.%3N
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However Splunk is still splitting on the other time stamps within the XML. So, what am I doing wrong?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Mar 2012 20:30:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89682#M4892</guid>
      <dc:creator>colinj</dc:creator>
      <dc:date>2012-03-12T20:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: TIME_FORMAT and XML</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89683#M4893</link>
      <description>&lt;P&gt;Are you editing the correct props.conf? (i.e. where the parsing occurs).&lt;BR /&gt;
If you have a Universal Forwarder -&amp;gt; Indexer OR Lightweight Forwarder -&amp;gt; Indexer setup, the props.conf to edit is on the Indexer.&lt;/P&gt;

&lt;P&gt;If you are using a full/heavy forwarder, the settings should go there.&lt;/P&gt;

&lt;P&gt;Apart from that your settings look good. You could possibly further qualify your TIME_PREFIX regex with (if tour 'real' timestamps are the actually in the beginning of the line);&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;TIME_PREFIX=^\[&lt;/CODE&gt;  &lt;/P&gt;

&lt;P&gt;How have you configured linebreaking? I'd recommend that you use&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;SHOULD_LINEMERGE=false
LINE_BREAKER = ([\r\n]+)\[\d\d
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which explicitly tells splunk to break events after a newline followed by the beginning of a 'real' timestamp.&lt;/P&gt;

&lt;P&gt;Hope this helps. If not, please give us more of your props.conf, and perhaps some more sample events.&lt;/P&gt;

&lt;P&gt;/Kristian&lt;/P&gt;</description>
      <pubDate>Mon, 12 Mar 2012 21:10:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89683#M4893</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-03-12T21:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: TIME_FORMAT and XML</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89684#M4894</link>
      <description>&lt;P&gt;Thanks! That did the trick.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Mar 2012 21:36:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/TIME-FORMAT-and-XML/m-p/89684#M4894</guid>
      <dc:creator>colinj</dc:creator>
      <dc:date>2012-03-15T21:36:23Z</dc:date>
    </item>
  </channel>
</rss>

