Lilac, a configuration tool for Nagios 3 now has an alpha release, testers wanted!

[Taylor Dondich]

Lilac, a configuration tool which was derived from Fruity, a popular
configuration tool for Nagios, has released it's first alpha release.
This release can be downloaded to create new Nagios configurations and
manage them.  It supports all of Nagios's object types as well as
multiple inheritance.  Lilac goes a step further with templates and
lets you bind services, escalations and dependencies to host templates
as well.  The alpha release features a rich exporter system as well.
The first alpha release does not have a completed configuration
importer (but does come with a basic Nagios configuration to start
from), nor does it have the auto-discovery feature.  Those will be
provided in the next Alpha release.  For now, Lilac needs people to
test the functionality of the UI and file bug reports or feature
requests to help make Lilac the best configuration tool out there for
Nagios.

For more information, take a look at the Lilac homepage at
http://www.lilacplatform.com for download links, basic install
documentation, forums, and issue tracking.

Thanks all, and for those who knew about this project, it's been a
long time coming!

-- 
Taylor Dondich
Check out Lilac, a configuration tool for Nagios 3 at
http://www.lilacplatform.com

Check out my Shortcut with O'Reilly Press:
Network Monitoring with Nagios:
http://oreilly.com/catalog/9780596528195/index.html

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null