Am 05.05.2011 12:43, schrieb nap:

On Thu, May 5, 2011 at 12:22 PM, Hienz, Michael <> wrote:

Hi Jean,



I am not sure which merlin db version you used when coding the broker for it, but my suggestion would be to use the merlin 0.9.0 one. This is the latest stable one and the one they are currently developing on. In regards to the reports the Ninja itself install will take care about the additional tables needed and the broker itself, does not need to feed those, because it’s pulling the information from the exsting merlin tables.

One question I have though, with the 0.5.6 version of Shinken. There now is a module to run the “old” Nagios command pipe, which is great, because when using Ninja adding comments or downtimes for example, these are submitted to the nagios.cmd. (That is stuff not working in your VMWare Virtual box builds). Nevertheless when I add a comment to a host through Ninja, it successfully makes the entry and I can see that comment in the Thruk frontend for example, but it does not appear on the Ninja frontend, because the corresponding db table is not filled with that data. I assume (haven’t checked this yet) that the merlin daemon usually needs to fill that piece of data, so it’s not done by Ninja itself.

Yes, it is just tables we do not fill right now I think. I didn't work on this module since months, because no one seems to mix Shinken and Ninja, but if you want it, it will raise in my priority tasks :)

That would mean that the merlin broker, needs to be adjusted in a way that all kind of commands coming through Ninja frontend (acknowledgements, comments, scheduled downtimes, etc.) are inserted into the merlin db. I am not sure how big your focus is on this frontend support, because I have seen you mentioning that Ninja is not multi daemon compatible and if you use multiple daemons in shinken, you just see half of the checks made. On the other hand it’s a good frontend, especially in the reports area, and this kind of functionality is always a good “seller”, when talking to the decision makers. J

The multi daemon problem was with a old version, I think now this should be solved in a current Ninja version, I'll try to look if it's good or not :)

The problem with Ninja is that it will never manage some main shinken features like root problem/uimpact + criticity for example, and it's quite a big miss for users I think. But if you want to run with it, especially with the good reporting module, it can be good to upgrade the module for new versions :)




Hi Jean,
the last few days/weeks I tried to implement the criticity feature to the Ninja UI.
I used a sandbox DB with one extra column each table(Host:criticity & Service:criticity). This way the sql query is quite simple.
I'm not so good in MySQL and PHP but this is my result of playing uround with Shinken and Ninja.

If you think it makes sence to fork the Ninja UI, please let me know.