I’d suggest how
icinga2 --version works in detecting the OS and type details.
I’d suggest how
Thanks, @dnsmichi . I’ll take a look into this. Simpler OS recognition is definitely a thing we want.
@l13t I believe there’s still some work to do so we initially detect where we are running and then use the right checks afterwards. There is a bit there of that logic but it’s still some way to go. Thanks for your input.
It’s on me to say thank you. I’m really stunned that this project which had the status of a quick hack just yesterday now already has two merged PR’s with actual benefits. You’re awesome!
I’ve got a github account but no git environment at the moment, so “sorry” for doing it this way.
The archive contains several files for different changes:
...GIT : the version from git the changes are based on ...SLES: changes for SLES detection ...VIRT: execution as non-root issues a hint now ...OMD : Icinga2 is contained in OMD as well, so some additional checks ...CHK : output of the object type when checking "check_interval"
In case not all changes should be included the files were changed in the following order:
GIT -> SLES -> VIRT -> OMD -> CHK
icinga-diagnostics.tgz (3.9 KB)
Wow, thanks. I’ll look into this.
@Wolfgang Just to let you know: Your changes were applied and are already in the current master. Thank you again for your contribution!
Just to let you know: I added “Projects” to the GitHub Repo where we can go on collecting ideas for the “suggestion mode” and the “anomaly detection”.
By the way, thanks for your contributions, all. They are very welcome.