<?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 NTP field extraction in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34814#M7571</link>
    <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I wanted to know what would be the best way to extract the st (stratum) field from the&lt;BR /&gt;
NTP event (in this case its 2). My goal is to get alerted when it turns 16 to notify my when NTP is out of sync &lt;/P&gt;

&lt;P&gt;Here is the log as it gets indexed in splunk&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*192.168.1.25     124.16.150.20   2 u   56   64  377    0.249   16.252   6.991
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;host=hostname   Options|  sourcetype=ntp   Options|  &lt;/P&gt;

&lt;P&gt;Thank you, &lt;/P&gt;</description>
    <pubDate>Tue, 14 Aug 2012 18:48:49 GMT</pubDate>
    <dc:creator>tevgey23</dc:creator>
    <dc:date>2012-08-14T18:48:49Z</dc:date>
    <item>
      <title>NTP field extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34814#M7571</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I wanted to know what would be the best way to extract the st (stratum) field from the&lt;BR /&gt;
NTP event (in this case its 2). My goal is to get alerted when it turns 16 to notify my when NTP is out of sync &lt;/P&gt;

&lt;P&gt;Here is the log as it gets indexed in splunk&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*192.168.1.25     124.16.150.20   2 u   56   64  377    0.249   16.252   6.991
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;host=hostname   Options|  sourcetype=ntp   Options|  &lt;/P&gt;

&lt;P&gt;Thank you, &lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2012 18:48:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34814#M7571</guid>
      <dc:creator>tevgey23</dc:creator>
      <dc:date>2012-08-14T18:48:49Z</dc:date>
    </item>
    <item>
      <title>Re: NTP field extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34815#M7572</link>
      <description>&lt;P&gt;yoursearch | rex "\d+.\d+.\d+.\d\s+\d+.\d+.\d+.\d\s+\s+(?&lt;STRATUM&gt;\d+)&lt;/STRATUM&gt;&lt;/P&gt;

&lt;P&gt;or&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;| multikv&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;This might just take the column headers and extract everything into the fields you need for you.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2012 19:20:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34815#M7572</guid>
      <dc:creator>dmaislin_splunk</dc:creator>
      <dc:date>2012-08-14T19:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: NTP field extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34816#M7573</link>
      <description>&lt;P&gt;When I run the search I get the same results. Should I be inputting any other parameters ?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2012 21:13:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34816#M7573</guid>
      <dc:creator>tevgey23</dc:creator>
      <dc:date>2012-08-14T21:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: NTP field extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34817#M7574</link>
      <description>&lt;P&gt;I was able to run the search using the multikv command and extracted the st field.  Then, I simply added a where command to see if my servers had drifted.  Here's the search:&lt;BR /&gt;
index=timevaraince | multikv | where st &amp;gt; 16 &lt;/P&gt;

&lt;P&gt;I'm building a time variance app and should have it up on splunkbase soon.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2013 03:16:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34817#M7574</guid>
      <dc:creator>amiracle</dc:creator>
      <dc:date>2013-07-22T03:16:57Z</dc:date>
    </item>
    <item>
      <title>Re: NTP field extraction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34818#M7575</link>
      <description>&lt;P&gt;Here's the app I built that helps you take apart the ntp output: &lt;A href="http://apps.splunk.com/app/1567"&gt;http://apps.splunk.com/app/1567&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
It's called Time Variance and it simply takes the output and lets you have a simple dashboard that shows the overall time variances on your multiple servers. I hope this helps you out.&lt;/P&gt;

&lt;P&gt;-K&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2013 14:16:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/NTP-field-extraction/m-p/34818#M7575</guid>
      <dc:creator>amiracle</dc:creator>
      <dc:date>2013-08-21T14:16:17Z</dc:date>
    </item>
  </channel>
</rss>

