Task #850
closedInvestigate a new way for check smartgears container by nagios
100%
Description
At this time we have a simple nagios check on tomcat port but this check often is not enough.
If a container, for some reasons, is not longer registered on the infrastructure for some time, the nagios check on tomcat port doesn't detect this problem.
A possible way for enhance the nagios check could be the following:
Every Smartgears node has an enabling service: Whn-Manager. This service could be checked via http for verify the container status.
For example, this url (related to node2-d-d4s.d4science.org): http://node2-d-d4s.d4science.org:8080/whn-manager/gcube/resource/ responds with a "resource is active" string.
What happen if this container, for some reasons, is no longer registered to the Infrastructure? What answer will be provided by this url?
if the answer is "the resource is not active", we have found a more specific nagios check.
There is a way to check this behavior?
Related issues