<?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: Monitor Proliant hardware in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79772#M181759</link>
    <description>&lt;P&gt;I suspect the most appropriate way to handle this would be via SNMP polling.  &lt;/P&gt;

&lt;P&gt;This hopefully can get you started:  &lt;A href="http://splunk-base.splunk.com/answers/38219/snmpget-with-splunk"&gt;http://splunk-base.splunk.com/answers/38219/snmpget-with-splunk&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jun 2012 21:42:09 GMT</pubDate>
    <dc:creator>sbrant_splunk</dc:creator>
    <dc:date>2012-06-25T21:42:09Z</dc:date>
    <item>
      <title>Monitor Proliant hardware</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79770#M181757</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Does anyone have Splunk monitoring HP Proliant servers for raid, psu, nic failures etc? If so, how did you go about that?&lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;

&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2011 10:03:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79770#M181757</guid>
      <dc:creator>bazcurtis</dc:creator>
      <dc:date>2011-09-22T10:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Proliant hardware</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79771#M181758</link>
      <description>&lt;P&gt;I have the same question as the OP?  Anyone have an answer?&lt;/P&gt;

&lt;P&gt;Thx&lt;BR /&gt;
dan&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jun 2012 20:50:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79771#M181758</guid>
      <dc:creator>dtorizuka</dc:creator>
      <dc:date>2012-06-25T20:50:02Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Proliant hardware</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79772#M181759</link>
      <description>&lt;P&gt;I suspect the most appropriate way to handle this would be via SNMP polling.  &lt;/P&gt;

&lt;P&gt;This hopefully can get you started:  &lt;A href="http://splunk-base.splunk.com/answers/38219/snmpget-with-splunk"&gt;http://splunk-base.splunk.com/answers/38219/snmpget-with-splunk&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jun 2012 21:42:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-Proliant-hardware/m-p/79772#M181759</guid>
      <dc:creator>sbrant_splunk</dc:creator>
      <dc:date>2012-06-25T21:42:09Z</dc:date>
    </item>
  </channel>
</rss>

