Hello,
For Shinken 1.6:
1. Re-implement check_shinken to actually use PYRO to talk to each
daemon and get pertinent statistics to actually determine that a
daemon is really running. The same logic would apply to the arbiter,
the current "ping" is inadequate and leads to cases where daemons
are actually not doing what they are supposed to. Identify key
metrics for each daemon, implement a function to expose them and
rewrite check_shinken to use it.
2. Splitting packs, modules and core is a good idea, I have no opinion
on how to go about doing this, but things seem to be looking up. Go
team.
3. Implement RPN + logic functions for bug-less triggers. We will be
working on this.
4. Optimize Mongodb logstore functions for Livestatus so that it is
actually usable in large installations. So that we can finally drop
sqlite.
5. -1 for Implementing more database back ends. We should focus on
making what we have work well.
6. Focus on a solid 1.6 release with bug fixes and good plumbing.
7. Commit new stuff to the development branch..
Cheers,
xkilian
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
