Project

General

Profile

Actions

Task #850

closed

Investigate a new way for check smartgears container by nagios

Added by Roberto Cirillo over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
System Application
Target version:
Start date:
Apr 01, 2016
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development, Pre-Production, Production

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

Related to D4Science Infrastructure - Task #3140: Improve nagios checks for gCore containerClosedAndrea Dell'AmicoApr 05, 2016

Actions
Related to D4Science Infrastructure - Task #3157: Improve the nagios check for the Smartgears (not the smart executor ones) nodesClosedAndrea Dell'AmicoApr 07, 2016

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)