Hi all, Like you know, the 0.2 version (bold badger) is for bugs hunting and industrialization. There are some important tickets in progress (https://sourceforge.net/apps/trac/shinken/report/2). The two majors are notification re-work and site/doc read from a English point of view :)
For the notification, Gerhard is working on a more easily notification code. Current one is something asynchronous that look at reactionner returns. That work for classic notifications and escalations, but with downtimes it far more hard to be sure it's ok in all cases. That why a cleaner (and easier code) is important here. Another point is the site/doc read from an English spoken person. Like you already know, my English skill are... not good :) And I'm happy to see someone look at the website and the documentation. Thanks to Luke L for this (I remember the Thanks file ;) ). I'm currently working on a problem/incident thing in experimental for the 0.2 version (should be ok in 0.4). The idea is to have the same thing than for notification but in real time monitoring (consoles). In the notification code, only "root problems" are notified. For example, if a server got a gateway router as a parent, if the gateway is down, there will be no notification DOWN for the server (just Unreach, but no one send them I think...). But for real time monitoring, for service, they are critical or warning, and we cannot see easily in all web interfaces what are the root problems of theses incidents (ITIL inside). That why I'm thinking about adding such informations in the 0.2 version in experimental. I hope some web interfaces will use it to give the users a new cool web pages : roots problems, and if the user click on it, it see the impacts (incidents in the ITIL world). And if the user look at an incident, he can see the root problem too. There will be a huge layout work in the next weeks too. I just wait a little because there is a magazine talking about Shinken with launch examples with the current layout this month (Linuxmag Fr). When they all launch it, we will change the layout with a real one (bin, lib, libexec, etc) and then make distributions packets :) There are other easy tasks in the trac if someone want to look at the code ;) Jean ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
