[Fiware-technical-committee] Global Instances monitorization

[FERNANDO LOPEZ AGUILAR]

Dear all,

Following the AP-16.03.07-5, the actions that Chapter leaders will have to take care of regarding monitoring of GE Global instances, were showed in this presentation (https://docs.google.com/presentation/d/1xJXKyjdY_u6kSeN8P2KHm3Rtnq0Mx57k59zSMd-eYO8/edit#slide=id.gedfaa15e9_0_7). The idea is any global instance that we have published in the FIWARE Catalogue MUST be always up and running. The solution adopted is based in the installation and configuration of Nagios tool in which we create jobs to check that the Global Instances are up and running anytime. The actions, that should be taken by FIWARE Chapter leaders, are the following:

  *   Step 1: Each Chapter leader has to identify his/her Global Instances in FIWARE Catalogue corresponding to his/her chapter. It could be possible that the FIWARE Catalogue is not up to day, so you should push the GE owner to update the FIWARE Catalogue. I created an initial list of them in the following document (https://docs.google.com/spreadsheets/d/1Zfv4qkucYrp0RfkG2SITXk-_rPsaB_-bE8xFNnWV_SU/edit#gid=0) but this list was referenced to January and could be extended if new Global Instances have to be added in your chapter. Please update accordingly the table with this information. In the same way, if you appreciate that some of the Global Instances should not be added to the list due to several reasons, you can delete it from the list.


  *    Step 2: For each GE(r)i not monitored, each Chapter leader should contact its owner in order to request the process to check that this Global Instance is up and running. Usually it should be the same process identified in the Sanity Checks process. The steps that should be performed by each owner:
     *   Step 2.1:  Basically if there is a response in the specific port, you should specify which IP, Port and Protocol are used. Example:

check_http --port 8080
check_http --ssl --port 9090
check_http -H 192.168.1.50 -p 8080

Please add this information in the comments row in the previous document. You have some example in the following page http://linux.101hacks.com/unix/check-http/

     *   Step 2.2:  Contact person or group (email) that will receive the notifications and responsible to resolve any detected issue in the Global Instance. Please add the proper info in the contacts row in the previous document.


     *   Step 2.3: If the Global Instance does not have http interface, we need to know how to test if it is up and running. Please describe it in the Comments row.

Best regards,
    Fernando.-

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20160503/464bd7f4/attachment.html>