Le 14/11/05 09:46, nap claviotta :
> On Tue, Nov 4, 2014 at 6:00 PM, Sebastien Coavoux <s.coav...@free.fr> wrote:
> 
> > Shinken community feedback :
> > We got feedback from people that allow us to list most highlighted
> > features to use Shinken :
> >     - Nagios configuration compatibility
> >     - Scalability / Realm
> >     - High customization with modules
> >     - High availability feature
> >
> > To conclude this part we state that Shinken was not a "must-have" for
> > small IT structure but for bigger one.
> >
> Just a remark: if you did choose Shinken for another reason we will be hapy
> to know it. The better we know the framework use case, the better we can
> improve it in the good way :)
> 

Several years ago, I chose Shinken thanks to your awesome « Gnu-Linux
Magazine France Hors Série ». At the time, I was a student using
Shinken on a very small IT structure, and yes, it was a "must-have".
Everything seemed so simple compared to Nagios documentations. 

For beginners, I believe that a good tutorial in many language is a
must have. Not a documentation, a tutorial. You know the difference.
Moreover, tutorial do not needs for frequent updates. The first
chapters of your GLMF are still completely usable in Shinken 2.0.
Complementary tutorials could be « how to monitor… (linux|windows…) ».
I know we already have that in the documentation, but working
instructions and example would be better.

Today, I also use Shinken in my company. 100 hosts for now, about 25
services each, and *nothing* in /etc/shinken/services… 

What I really love about Shinken are the packs. I have never tested
Nagios or Icinga, maybe there is a similar approach to configure the
hosts ? Packs are really awesome because you just install them, use
them in your hosts, and it's done ! You don't even have to understand
how they work, they just do. Moreover, packs force you to define a
monitoring strategy : What types of equipment did I have ?  What
services did I associate to each type ? And then, I stick to the plan.

But for packs to be even more awesome, there is some work to do in
them. Look at pack-oracle for example. It is so great to have a pack
for Oracle. So why does this pack didn't include the plugin
check_oracle_health ? Why are $ORACLEUSER$ and $ORACLEPASS$ declared
in macros.cfg and not in the template !? I don't wait for answers
here. In fact, I don't care, I don't have oracle servers. This is just
an example. But you should really pay attention to those details,
because ready-to-use Packs, like mysql, are killer feature.

Oh, and « shinken install » should be able to install a git repo.


Thanks for the news, by the way. Long life to Shinken :)

-- 
Guillaume Subiron 
  Mail - maet...@subiron.org
   GPG - 5BC2 EADB
Jabber - maet...@im.subiron.org
   IRC - maethor@(freenode|geeknode)

------------------------------------------------------------------------------
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to