<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" version="2.0">
  <channel>
    <title>Recent Posts by Matt | Beast</title>
    <link>http://forums.scoutapp.com/users/10/posts</link>
    <language>en-us</language>
    <ttl>60</ttl>
    <atom:link href="http://forums.scoutapp.com/open_search.xml" rel="search" type="application/opensearchdescription+xml"/>
    <item>
      <title>Plugins WANTED! replied by Matt @ Sat, 19 Apr 2008 20:49:37 -0000</title>
      <description>&lt;p&gt;What about an interface to monit? The monit folk recently released their &amp;#8220;m|monit&amp;#8221; project (&lt;a href="http://tildeslash.com/mmonit/"&gt;http://tildeslash.com/mmonit/&lt;/a&gt;).&lt;/p&gt;


	&lt;p&gt;Scout looks a heck of a lot cooler, has a great, defined plug-in interface, is much further along, and doesn&amp;#8217;t require &lt;strong&gt;another&lt;/strong&gt; process running (should monit monitor m|monit, too??)&amp;#8212;in short, it seems like a far superior solution.&lt;/p&gt;


	&lt;p&gt;What about a plugin that lets you interface with the monit process already running on our servers? I see the plugin library already has a simple script to restart mongrel. But the monit process monitoring/restarting syntax is significantly more advanced: why re-invent the wheel?&lt;/p&gt;


	&lt;p&gt;It could start out simply enough: interrogate the monit conf file and execute commands held within, but seems a short hop to then replace all that m|monit does.&lt;/p&gt;


	&lt;p&gt;Interested in the everyone&amp;#8217;s thoughts!!&lt;/p&gt;


	&lt;p&gt;Thanks,&lt;/p&gt;


	&lt;p&gt;&amp;#8212;&lt;br /&gt;Matt&lt;/p&gt;</description>
      <pubDate>Sat, 19 Apr 2008 20:49:37 -0000</pubDate>
      <guid isPermaLink="false">forums.scoutapp.com:2:5:21</guid>
      <author>Matt</author>
      <link>http://forums.scoutapp.com/forums/2/topics/5</link>
    </item>
  </channel>
</rss>
