<?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 Solaris monitoring using Splunk in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33928#M69726</link>
    <description>&lt;P&gt;I am New to Spluk &amp;amp; installed indexer on windows server &amp;amp; forwarder on Solaris Sparc.&lt;BR /&gt;
Now I would like monitor below types of &lt;/P&gt;

&lt;P&gt;Change in system value &lt;BR /&gt;
Pkg installation details ( if any new package installed, that should detect by Splunk)&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2013 12:02:51 GMT</pubDate>
    <dc:creator>catch_mili</dc:creator>
    <dc:date>2013-02-15T12:02:51Z</dc:date>
    <item>
      <title>Solaris monitoring using Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33928#M69726</link>
      <description>&lt;P&gt;I am New to Spluk &amp;amp; installed indexer on windows server &amp;amp; forwarder on Solaris Sparc.&lt;BR /&gt;
Now I would like monitor below types of &lt;/P&gt;

&lt;P&gt;Change in system value &lt;BR /&gt;
Pkg installation details ( if any new package installed, that should detect by Splunk)&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2013 12:02:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33928#M69726</guid>
      <dc:creator>catch_mili</dc:creator>
      <dc:date>2013-02-15T12:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: Solaris monitoring using Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33929#M69727</link>
      <description>&lt;P&gt;Hi catch_mili&lt;/P&gt;

&lt;P&gt;you can either monitor the &lt;CODE&gt;/var/sadm/pkg&lt;/CODE&gt; directory for package installation or run scripted input from &lt;CODE&gt;pkginfo -l&lt;/CODE&gt;.&lt;BR /&gt;
What do you mean by &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;EM&gt;Change in system value&lt;/EM&gt; &lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;do you want monitor &lt;CODE&gt;/etc/system&lt;/CODE&gt; ?&lt;/P&gt;

&lt;P&gt;cheers,&lt;BR /&gt;
MuS&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2013 13:27:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33929#M69727</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-02-15T13:27:30Z</dc:date>
    </item>
    <item>
      <title>Re: Solaris monitoring using Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33930#M69728</link>
      <description>&lt;P&gt;Also I do think this is more of a Solaris question than a Splunk question. "How can I monitor this in Solaris?" is one question - after that it's just a matter of getting that data into Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2013 13:41:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33930#M69728</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-02-15T13:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Solaris monitoring using Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33931#M69729</link>
      <description>&lt;P&gt;Here are some of the most likely logs you will want to monitor:&lt;/P&gt;

&lt;H2&gt;/var/log/sulog&lt;/H2&gt;

&lt;P&gt;The sulog file, /var/adm/sulog, is a log containing all attempts (whether successful or not) of the su command. &lt;/P&gt;

&lt;H2&gt;/var/adm/loginlog&lt;/H2&gt;

&lt;P&gt;Unsuccessful login attempts after five consecutive failures are logged in the file /var/adm/loginlog&lt;/P&gt;

&lt;H2&gt;/var/adm/messages&lt;/H2&gt;

&lt;P&gt;This log records system console output and syslog messages.&lt;/P&gt;

&lt;H2&gt;/var/adm/pacct&lt;/H2&gt;

&lt;P&gt;This log records the commands run by all users. Process accounting must be turned on before this file is generated. &lt;/P&gt;

&lt;H2&gt;/var/adm/messages&lt;/H2&gt;

&lt;P&gt;This file is a catch-all log file for a number of messages from the UNIX kernel as well as for other logging applications such as syslogd. The file is formatted as an ASCII text file and entries are usually one record per line with new entries appended to the end of the file. &lt;/P&gt;

&lt;P&gt;You can use the [Monitor] directive to monitor the log files:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitorfilesanddirectories"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitorfilesanddirectories&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2013 14:16:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Solaris-monitoring-using-Splunk/m-p/33931#M69729</guid>
      <dc:creator>colbra</dc:creator>
      <dc:date>2013-02-15T14:16:46Z</dc:date>
    </item>
  </channel>
</rss>

