[Fiware-monitoring] testing with Nagios plugin for IoT Discovery global instance

[PABLO RODRIGUEZ ARCHILLA]

Dear Tarek.

At the moment we avoid using credentials/auth headers when checking services. We know this narrows our choices, but handling with authentication introduces several problems.

So we could:


-          Either just checking TCP/80 (command = check_tcp!80)

-          Or check HTTP but expecting the a 401 status code (command = check_http!--port=80 --onredirect=follow --url=/s2w/ --expect=401)

Both are equivalent (in any case we check the “real” service), so maybe first choice is the simplest and better.

Regards.


--
Pablo Rodríguez Archilla

  FIWARE Initiative

(+34) 958 53 79 02 / 91 31 29119

  Product Innovation

pablo.rodriguezarchilla at telefonica.com 

  Telefónica I+D

Edificio I+D Armilla (Parque Tecnológico de la Salud), Granada, Spain


De: fiware-monitoring-bounces at lists.fi-ware.org [mailto:fiware-monitoring-bounces at lists.fi-ware.org] En nombre de t.elsaleh at surrey.ac.uk
Enviado el: sábado, 14 de marzo de 2015 17:07
Para: fiware-monitoring at lists.fi-ware.org
Asunto: Re: [Fiware-monitoring] testing with Nagios plugin for IoT Discovery global instance

Hello,
I managed to successfully test my GEi using the command below:

/usr/lib/nagios/plugins/check_http -H iot-discovery.lab.fiware.org --port=80 --onredirect=follow --url=/s2w/ --header=X-Auth-Token:Fe2rv78                                      xwhcYE-EY6C84Koyg_VAWTMm_ULzsBS73sNZjEZTx6VQkYoMRa83v3CO4_Ea2U04HbVxZoFLXHkQrAw

The issue is that my GEi works behind the PEP proxy (via port 80). Therefore I need to feed the keyrock token in the test. Should I also specify this in the config files, if so where?

Best regards,
Tarek




From: Elsaleh T Mr (Electronic Eng)
Sent: 13 March 2015 16:22
To: 'fiware-monitoring at lists.fi-ware.org'
Subject: testing with Nagios plugin for IoT Discovery global instance

Hello,

I am trying to test the following command but I get an error:

/usr/lib/nagios/plugins/check_http -H iot-discovery.lab.fiware.org -k X-Auth-Token=Fe2rv78xwhcYE-EY6C84Koyg_VAWTMm_ULzsBS73sNZjEZTx6VQkYoMRa83v3CO4_Ea2U04HbVxZoFLXHkQrAw  --port=80 --onredirect=follow --url=/

HTTP CRITICAL - No data received from host

Even though I have tested using a REST client and it works. Would you know what I am doing wrong here?

Best regards,
Tarek


________________________________

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-monitoring/attachments/20150316/583b03ea/attachment.html>