Hey Thanks a lot for such a worthy and elaborate description.
I have one more query. Pandora FMS enterprise licensing mentions: "Artica ST Enterprise License, with full access to source code, and restricted distribution and usage".
What exactly it mean when it says "RESTRICTED DISTRIBUTION AND USAGE"??????
--- On Sat, 16/2/13, General mailing list for Pandora FMS users. <pandora-public@...> wrote:
> From: General mailing list for Pandora FMS users. <pandora-public@...>
> Subject: Re: [Pandora-public] Pandora FMS Enterprise features
> To: "General mailing list for Pandora FMS users. " <pandora-public@...>
> Date: Saturday, 16 February, 2013, 4:08 AM
> Hi Shivangi,
> > I am going through the differences between pandora FMS
> open source and Enterprise version, facing certain queries
> in the understanding of some features.
> > 1. Centralized Management using monitoring policies
> > The product document says this feature is include to
> facilitate administrator's job. But what are policies? how
> they facilitates the working?
> With open source, when you need to change a configuration in
> the agent, you need to edit the file itself, accessing by
> SSH and/or Terminal server to the server, edit the conf and
> restart the agent.
> Ok, what happen if you have 500 servers monitored ?
> What happen if you want to have the same configuration in
> different groups (databases, front ends, backup servers,
> antivirus) or even worst, you want a "basic" layer (disk,
> mem, cpu) on all of them, BUT personalize on different
> groups ?, you can do with your own scripts, but that will
> take a lot of time.
> Policies allows you to manage remotely the configuration by
> using templates and apply them to the agents, by "pushing"
> the configuration to the agens, on a single click, on the
> console. All the templates are applied in the same way for
> all selected agents, you will be sure the monitoring modules
> are exactly the same on all of them. You can set exceptions,
> of course.
> And that doesn't include the configuration on the agent
> side, that includes also the threshold for critical/warning
> values, post processing, description, etc. You manage the
> configuration in the "global way", not system by system.
> > 2. Monitoring with weight
> Thats service monitoring. It's complex to explain, please
> refer to documentation, but I will write a single example:
> You have a cluster of frontend servers (10 servers), now if
> one is down, you receive an alert. A cluster is suppose to
> be to give you margin on failures. With service monitoring,
> you can define weights, and write a rule to warn you only
> when 3 servers of more are down, and do something more
> drastic (like booting up a reserve server) when 5 servers
> are down.
> > 3. Centralized file distribution system
> You can "push" files to your agents (to be used as agent
> plugins, for example). That could be done system by system,
> or using policies to push a file distribution on all
> systems. You can use that to distribute software also, of
> Un saludo
> Sancho Lerena
> The Go Parallel Website, sponsored by Intel - in partnership
> with Geeknet,
> is your hub for all things parallel software development,
> from weekly thought
> leadership blogs to news, videos, case studies, tutorials,
> tech docs,
> whitepapers, evaluation guides, and opinion stories. Check
> out the most
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> Pandora-public mailing list