<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   ***: toeshred has joined #arpnetworks
   <br> dwarren_ has joined #arpnetworks
   <br> dwarren has quit IRC (Read error: Connection reset by peer)
   <br> mike-bur1 is now known as mike-burns
   mnathani_: if one was to setup a new monitoring box, would nagios still be preferred over icinga or are they basically the same?
   brycec: I haven't touched Icinga, but I prefer Monit (and M/Monit) over Nagios fwiw
   mnathani_: k
   plett_: Personally, I would still use Nagios because it's what I know. I would do everything possible to not write config for it manually though - I'm a big fan of having your config management system build nagios config at the same time as deploying a service
   ***: qbit has quit IRC (Ping timeout: 240 seconds)
   mercutio: i was all excited about having higher upload speed, and now i have nothing to upload.
   <br> monitoring solutions always seem to be a bit messy, most people go with what they're familiar with.
   <br> and like plett said if you can automate config, it makes things simpler if you have a larger environment
   <br> if you have smaller config and want to just check availability you may be better off using external monitoring
   <br> munin is kind of nifty too
   ***: qbit has joined #arpnetworks
   brycec: Munin is decent for charting, but I find that munin-limits is somewhat terrible, primarily it's surprisingly CPU-heavy.
   mercutio: well charting is good for passive stuff
   <br> and external monitoring is good for availability
   <br> i'd actually been finding smokeping kind of nifty for alerting too
   <br> like if a web page loads slow
   ***: jcv_ has quit IRC (Quit: leaving)
   <br> jcv has joined #arpnetworks
   <br> mjp_ has joined #arpnetworks
   <br> tabthorpe has quit IRC (Read error: Connection reset by peer)
   <br> tabthorpe has joined #arpnetworks
   mnathani_: I got nagios going for the most part. An annoying permission issue I can't seem to fix
   <br> Apache web server: You don't have permission to access /nagios/index.php on this server.
   mjp_: sounds like basic apache config
   ***: meingtsil has joined #arpnetworks
   <br> meingtsla has quit IRC (Ping timeout: 264 seconds)
   <br> meingtsil is now known as meingtsla
   <br> dj_goku has quit IRC (Remote host closed the connection)
   <br> dj_goku has joined #arpnetworks