The Monitoring GE is a component that we are using internally in order to get all the monitoring information from the OpenStack environment in the same way that we use it to recover the monitoring information about the different instances deployed in the Cloud. I mean the current version take the information from the (virtual) machine and send it through NRPE to a Nagios plugin in order to proceed it.

Saying that, I do not have so clear the scenario in which you planned to use it. I mean, you want to monitor your instances like the rest of the instances or just use the Monitoring component in order to monitor your system outside the FIWARE Lab Cloud component.

Fernando

Fernando, please, to answer an external user you have to use email, writing a comment is valid for internal users.
Please, follow the directions below to do it right!
http://backlog.fiware.org/guide/tracker.html#email-issue

Thanks in advance!!

Dear Andrea,

The Monitoring GE is a component that we are using internally in order to get all the monitoring information from the OpenStack environment in the same way that we use it to recover the monitoring information about the different instances deployed in the Cloud. I mean the current version take the information from the (virtual) machine and send it through NRPE to a Nagios plugin in order to proceed it.

Saying that, I do not have so clear the scenario in which you planned to use it. I mean, you want to monitor your instances like the rest of the instances or just use the Monitoring component in order to monitor your system outside the FIWARE Lab Cloud component.

Fernando

Dear Fernando,

we have 2 different goals in our project.

The first one, which is *not *related to the Monitoring GES, is to use the
FIWARE Cloud API (namely the OpenStack API, aka* IaaS Resource Management
GE*) in order to programmatically instantiate VMs on the FIWARE
infrastructure.

We've just received (yesterday) the API endpoint; so we're going to try to
use it asap.

In a few words, in this first phase we need to investigate if we can
"threat" the FIWARE cloud infrastructure as a "public cloud" (that means we
need to check if the performances and the reliability are satisfying).

The second objective regards the Monitoring GE.

When we programmatically (via API) instantiate a VM on the cloud (I mean
"every" cloud, also public, like Amazon, CGE, Rackspace, etc. not only the
FIWARE infrastructure) we need to monitor it, eventually.

That means we need to setup in the newly created VM a monitoring agent
which push the IaaS metrics on a Monitoring System.

We already have a Monitoring System, which was developed from the scratch
by us, but in this project we need to investigate if the Monitoring GE can
substitute it.

For this reason we would like to have a private (or shared) running
instance of this Monitoring GE where we may push all the IaaS metrics we
collect from the VMs running all over the cloud, in order to check if the
Monitoring instance itself is stable, reactive, etc...

Is it possible?

TKS
A.

======================================================

Andrea Vecchi
CTO

mobile +39 349 6379920
skype: andreavecchi

ClouDesire Srl
Via Gozzini, 15/17 - 56121 Pisa (PI) - Italy
www.cloudesire.com | info@cloudesire.com
twitter: www.twitter.com/cloudesire
t +39 050877088 | f +39 0508755498

======================================================

Ai sensi del D. Lgs. n.196 del 30/06/2003 si precisa che le informazioni
contenute in questo messaggio sono riservate e ad uso esclusivo del
destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore,
La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie

This message, for the D. Lgs. n.196 of 30/06/2003, may contain confidential
and/or privileged information. If you are not the addressee or authorized
to receive this for the addressee, you must not use, copy, disclose or take
any action based on this message or any information herein. If you have
received this message in error, please advise the sender immediately by
reply e-mail and delete this message. Thank you for your cooperation.

On Tue, Feb 23, 2016 at 4:21 PM, Help-Desk <jira-help-desk@fi-ware.org>

Dear Andrea,

Well, it could be possible to install for your node the Monitoring GE in a VM in which you want to recover information from it. I think that it could be possible. Originally, the component was developed thinking about the monitoring of the OpenStack infrastructure.

But a deep analysis of it, give you the possibility to install the Nagios agent to recover the information of the VM and pass it to a Nagios system to deal with this information. In the same way we have defined some Nagios Plugin in order to publish the information to an external server using NGSI format. So, it could be possible to integrate the monitoring system which your own monitoring architecture in the same way that you can use the Monitoring GE to monitor your own VM.

Other topics is that eventually all the VM are provided with monitoring agents right now, so you can check the information from them.

This is related to the R4 of FIWARE, currently we are working in a new version of the Monitoring architecture using Ceilometer + Monasca API it is under development and we are testing it only in the Spain node.

I think that you can translate this question to StackOverFlow with tag fiware-monitoring in order to follow the requirements and specifying the way to use the Monitoring system GE there.

Dear Fernando,

thanks for this information.

You wrote me that all the VMs provisioned using your FIWARE OpenStack
instance are monitored by a centralized instance of the Monitoring GE.

Is it possible to have specific credentials to access to this centralized
Monitoring GE instance?

I'm asking you that, because we finally was able to use your OpenStack API
and now we can create new VMs programmatically. If is true that each of
that VMs have an agent preinstalled on them, we could use your centralized
Monitoring GE instance in order to push the collected metrics to our
dashboard.

Let us know,
TKS
A.

======================================================

Andrea Vecchi
CTO

mobile +39 349 6379920
skype: andreavecchi

ClouDesire Srl
Via Gozzini, 15/17 - 56121 Pisa (PI) - Italy
www.cloudesire.com | info@cloudesire.com
twitter: www.twitter.com/cloudesire
t +39 050877088 | f +39 0508755498

======================================================

Ai sensi del D. Lgs. n.196 del 30/06/2003 si precisa che le informazioni
contenute in questo messaggio sono riservate e ad uso esclusivo del
destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore,
La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi,
dandocene gentilmente comunicazione. Grazie

This message, for the D. Lgs. n.196 of 30/06/2003, may contain confidential
and/or privileged information. If you are not the addressee or authorized
to receive this for the addressee, you must not use, copy, disclose or take
any action based on this message or any information herein. If you have
received this message in error, please advise the sender immediately by
reply e-mail and delete this message. Thank you for your cooperation.

On Wed, Mar 2, 2016 at 8:54 AM, Help-Desk <jira-help-desk@fi-ware.org>

Usually, if there is no special restriction, you can obtain the information taking the Monitoring API, you only need a specific token that you can obtain with your user and password from the FIWARE Lab user account.

We are in a process to change the Monitoring API so in the meantime you have to wait a little but I suppose by the end of this release you can use the new API.

The new API is based on Monasca API, you can take a look in https://github.com/openstack/monasca-api/blob/master/docs/monasca-api-spec.md to know more about it.

Fernando

Comment by andrea.vecchi@cloudesire.com :
Hi Fernando,

any news about this?

*We are in a process to change the Monitoring API so in the meantime you
have to wait a little but I suppose by the end of this release you can use
the new API.*

we are close to the mid-term review of our project, and we would like to
start using this GE, which we expected to integrate...

Another question: are the old API available, at least?

Can you indicate me where the old API endpoint is?
maybe this?

https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Monitoring_Open_RESTful_API_Specification

Thank you in advance,
BR
A.

ANDREA VECCHI

CTO
andrea.vecchi@cloudesire.com
www.cloudesire.cloud | www.appshop.cloud
M: +39 3496379920

On Fri, Mar 4, 2016 at 4:27 PM, Help-Desk <jira-help-desk@fi-ware.org>
wrote:

> Usually, if there is no special restriction, you can obtain the
> information taking the Monitoring API, you only need a specific token that
> you can obtain with your user and password from the FIWARE Lab user account.
>
> We are in a process to change the Monitoring API so in the meantime you
> have to wait a little but I suppose by the end of this release you can use
> the new API.
>
> The new API is based on Monasca API, you can take a look in [
> https://github.com/openstack/monasca-api/blob/master/docs/monasca-api-spec.md]
> to know more about it.
>
> Fernando
>
>
> -------------------------------------------------------------------------------
> Fernando Lopez created HELP-5851:
> ------------------------------------
>
> Summary: [Fiware-soulfi-coaching] support request for
> Monitoring GE - TID Implementation
> Key: HELP-5851
> URL: https://jira.fiware.org/browse/HELP-5851
> Project: Help-Desk
> Issue Type: extRequest
> Components: FIWARE-TECH-HELP
> Reporter: FW External User
>
> This email was generated by the FIWARE JIRA (http://jira.fiware.org).
>

Esta solicitud acaba de ser enviada a:

• Time sent: 28/Apr/16 7:21 PM
• To: andrea.vecchi@cloudesire.com
• Cc: fernando.lopezaguilar@telefonica.com
• con el asunto: Use of Monitoring GE in SaaSi-FI project
  

Dear Andrea,

I read in your conversation with Fernando that you need to monitor every VM programmatically instantiated via API.

Monitoring GE itself does not help you with that. But you could take advantage of the developments of another FI-PPP project (XIFI) instead: what you need is the "DEM Adapter":

http://wiki.fi-xifi.eu/Public:PDEM

You could consider it as a "daemon" gathering metrics of your VM and sending them to an instance of FIWARE Context Broker ("Orion")

Obviously, this requires an automatic installation of the DEM when the VMs are instantiated. You could carry out this using a cloud-init post-creation script, like this:

	#cloud-config
	#
	# This script automatically permorm some needed actions for the VM configuration

	# Start DEM monitoring
	runcmd:
		 - curl -L -s -k https://xifisvn.esl.eng.it/wp3/software/DEM_Adapter/install.sh | bash

If you read the documentation, DEM queries metadata service to identify which region the VM belongs to. Therefore, every instantiation of VMs should include a "region" metadata item

On the other hand, Context Broker is supposed to listen at the following URL by default:

	http://cb.<region>.cloud.fiware.org:1026

In case you need to use your own instance, two configuration attributes should be adjusted in "/usr/local/vmMonitor/monitoring.cfg":

	cb_server
	cb_ports

Hope this clarifies.

Best regards.