Page Comparison

...

The following steps are a general guide:

1. In Abiquo, create an OAuth application in Abiquo for collectd. See Add an application for OAuth 

   1. Assign the privilege to  “Allow user to push own metrics”

2. Install collectd on your VM

3. Install the Abiquo collectd plugin (from source or using the Abiquo Chef cookbook).

   1. Configure the Abiquo API path to push the metrics to the VM in Abiquo. Check the correct format of the API path in the API documentation

4. Configure your metrics in collectd

The Abiquo collectd plugin will automatically push all collectd metrics to the Abiquo API in PUTVAL JSON format.

To display the VM metrics in Abiquo:

1. Edit your VM and go to Monitoring

2. Select Fetch metrics data. 

3. Optionally select the monitoring level on providers that support it, e.g. AWS 

4. Select the metrics to display from the custom metrics and the built-in metrics of the cloud provider or hypervisor
   

...

1. Image Added

2. Save your changes to the VM. Optionally define a scaling group to increase the number of VMs running your application automatic scaling actions. See Define a scaling group 

3. If your VM is not running, deploy to launch the VM. Wait several minutes for the server to return metrics

4. On the VM icon near the top right corner, click the metrics symbol. Or in the Virtual appliance, go to Monitoring → Virtual machines 

   Image Modified

5. Configure the metrics to display the required statistic, frequency, dimensions, and so on.

   Image Modified

   Image Modified

6. Create alarms to set metric thresholds and alerts on groups of alarms, to notify or respond to changing application conditions with automation using action plans. See Cloud VM automation guide

...

Automate the install of collectd using Chef

This is an example use case with Chef using the Abiquo Chef cookbook.

1. In Abiquo, the administrator creates an OAuth application in Abiquo for collectd. See Add an application for OAuth 

   1. Assign the privilege to  “Allow user to push own metrics”

2. On the Chef server, the administrator creates a role with the following:

   1. The monitoring recipes to install the Abiquo collectd plugin

   2. The OAuth tokens for the application configured

3. In Abiquo, users edit the VM and go to Chef, then select the appropriate collectd role.

Abiquo recommends this kind of automation because the OAuth application belongs to the tenant administrator. This means that the administrator prepares the configuration for users, it is easy to apply it automatically on a large scale, and the administrator can protect the configuration from accidental changes when users load their own Chef recipes, etc.

...