<?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 Server Uptime in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Server-Uptime/m-p/53007#M22284</link>
    <description>&lt;P&gt;How to major uptime of the server using splunk&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2013 14:28:56 GMT</pubDate>
    <dc:creator>catch_mili</dc:creator>
    <dc:date>2013-03-06T14:28:56Z</dc:date>
    <item>
      <title>Server Uptime</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Server-Uptime/m-p/53007#M22284</link>
      <description>&lt;P&gt;How to major uptime of the server using splunk&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2013 14:28:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Server-Uptime/m-p/53007#M22284</guid>
      <dc:creator>catch_mili</dc:creator>
      <dc:date>2013-03-06T14:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: Server Uptime</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Server-Uptime/m-p/53008#M22285</link>
      <description>&lt;P&gt;I'm assuming you mean "measure" the uptime. One way is to use a scripted input to ping the server. Then just do a stats on how often it doesn't respond. You can also use a forwarder and send some logs. The forwarder will send heartbeats and you will be able to know if it stops checking in.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2013 14:39:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Server-Uptime/m-p/53008#M22285</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2013-03-06T14:39:02Z</dc:date>
    </item>
  </channel>
</rss>

