Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8764
Created by jmeyer on 2015-03-16 13:59:00 +00:00
There's a bit more outdated stuff inside, and some sections in the general docs require updates as well.
In the section "Asynchronous Event Execution" as part of the chapter "Migration" it is stated that Icinga2 does not block when a check is being executed while at the same time it is stated that events and notifications each run in their own thread. (Utilizing the term "asynchronous" in both cases.) This is very likely causing the reader to think that Icinga2 spawns a new thread for each executed check, which it does not.
2015-03-19 17:03:01 +00:00 by (unknown) 0c0bae2
2015-03-19 17:03:48 +00:00 by (unknown) df99eab