<?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 monitor remote linux servers from a RedHat server? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9975#M238</link>
    <description>&lt;P&gt;There are a number ways of that you can get data from remote systems into your Splunk instance. &lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;You can install a forwarding agent on each of the machines that you wish to collect data from that will send events to the central indexer. More information on data cloning and routing can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Aboutforwardingandreceivingdata" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Aboutforwardingandreceivingdata&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;You can configure syslog/syslog-ng to forward event data to a central Splunk index. You will then configure Splunk to listen on the specified UDP (syslog) or TCP (syslog-ng) port. More information on configuring Splunk to listen on a network port can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitornetworkports" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitornetworkports&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;You can write a small script that collects the various files from your remote systems and feeds them into your index using our scripted input method. More information on scripted inputs can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/ScriptedInputsIntro" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/ScriptedInputsIntro&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Thu, 04 Mar 2010 02:26:57 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2010-03-04T02:26:57Z</dc:date>
    <item>
      <title>How to monitor remote linux servers from a RedHat server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9974#M237</link>
      <description>&lt;P&gt;I just installed splunk on RedHat enterprise 5, and want to know how to
monitor remote linux servers from RedHat server &lt;/P&gt;</description>
      <pubDate>Thu, 04 Mar 2010 02:25:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9974#M237</guid>
      <dc:creator>Alan_Bradley</dc:creator>
      <dc:date>2010-03-04T02:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor remote linux servers from a RedHat server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9975#M238</link>
      <description>&lt;P&gt;There are a number ways of that you can get data from remote systems into your Splunk instance. &lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;You can install a forwarding agent on each of the machines that you wish to collect data from that will send events to the central indexer. More information on data cloning and routing can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Aboutforwardingandreceivingdata" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Aboutforwardingandreceivingdata&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;You can configure syslog/syslog-ng to forward event data to a central Splunk index. You will then configure Splunk to listen on the specified UDP (syslog) or TCP (syslog-ng) port. More information on configuring Splunk to listen on a network port can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitornetworkports" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/Data/Monitornetworkports&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;You can write a small script that collects the various files from your remote systems and feeds them into your index using our scripted input method. More information on scripted inputs can be found here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/ScriptedInputsIntro" rel="nofollow"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/ScriptedInputsIntro&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Thu, 04 Mar 2010 02:26:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9975#M238</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2010-03-04T02:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor remote linux servers from a RedHat server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9976#M239</link>
      <description>&lt;P&gt;Since UDP is unreliable, would it be best just to rsync remote logs to the local instance on an interval?&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2011 03:21:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-remote-linux-servers-from-a-RedHat-server/m-p/9976#M239</guid>
      <dc:creator>inetbizo</dc:creator>
      <dc:date>2011-05-16T03:21:15Z</dc:date>
    </item>
  </channel>
</rss>

