With Fruity/Lilac, can you choose to update the config via the CLI as well as via the GUI, or is the config locked from making manual changes?
I ask because you mentioned repetitive changes not being easy with the GUI. -- Eric Cables On Tue, Apr 13, 2010 at 2:33 PM, Tony Bunce <[email protected]> wrote: > We use Fruity (Lilac requires PHP 5.2 and CentOS doesn't/didn't have rpms, > looks like they are in the 5.2 is in CentOS-Testing now though) and Nconf > (two different servers). > > Fruity/Lilac works well but isn't perfect. There are a few small > features/bugs that would make it much better: > -Copy Services/Host - when your setting up the same check 5,10,20 times > with just a different parameter it gets really repetitive. > -No way to edit check command parameters, you have to delete and re-add. > And if you have multiple parameters and want to change the first one you > have to delete and re-enter them all because there isn't a way to re-enter > them. > > > NConf has some nice features like showing you what each command arg means, > for example: > ARG1=web address > ARG2=url > ARG3=Additonal parameters > > But it also has its issues. When we started using NConf didn't have an > import feature, I think the latest version does though. NConfig also has a > Perl interface that can be used to automate configuration task. NConf also > doesn't deploy/export the config nearly as easily as Lilac. > > If I had to pick one over the other I would pick Fruity/Lilac, if it had a > programmatic interface or CLI it would be really nice. > > -Tony > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Eric Cables > Sent: Tuesday, April 13, 2010 4:59 PM > To: [email protected] > Subject: [c-nsp] Nagios config frontends > > Sorry if this is a bit OT, but I was wondering what configuration frontend > people have settled on for Nagios. I have been running Nagios for years > now > just with a flat configuration file, but I'd like to extend the > configuration tasks to others besides myself, and a web based GUI frontend > seems like the best way to do that. > > Lilac (previously Fruity) seems like a pretty solid choice, and I've also > heard good things about Monarch. > > Any suggestions, or confirmations of the above, would be appreciated. > > Thanks, > > -- Eric Cables > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
