zenoss / zenpacks.zenoss.cloudfoundry

CloudFoundry Monitoring

ZenPacks.zenoss.CloudFoundry

Please watch the Monitoring Cloud Foundry video for a quick introduction that covers most of the details below.

About

This project is a Zenoss extension (ZenPack) that makes it possible to monitor the capacity and performance of applications running on a Cloud Foundry platform. This works for applications hosted in a local micro-cloud or a hosted environment such as the one offered by VMware at cloudfoundry.com.

Cloud Foundry is an open PAAS (Platform as a Service) project initiated by VMware.

Installation

You must first have, or install, Zenoss 3.1.0 or later. Core and Enterprise versions are supported. You can download the free Core version of Zenoss from http://community.zenoss.org/community/download.

Normal Installation (packaged egg)

Depending on what version of Zenoss you're running you will need a different package. Download the appropriate package for your Zenoss version from the list below.

• Zenoss 4.1: Latest Package for Python 2.7
• Zenoss 3.0 - 4.0: Latest Package for Python 2.6

Then copy it to your Zenoss server and run the following commands as the zenoss user.

zenpack --install <package.egg>
zenoss restart

Developer Installation (link mode)

If you wish to further develop and possibly contribute back to the CloudFoundry ZenPack you should clone the git repository, then install the ZenPack in developer mode using the following commands.

git clone git://github.com/zenoss/ZenPacks.zenoss.CloudFoundry.git
zenpack --link --install ZenPacks.zenoss.CloudFoundry
zenoss restart

Usage

Once the CloudFoundry ZenPack is installed you can add endpoints by going to the infrastructure screen and clicking the normal button for adding devices. You will find a new option labeled, "Add CloudFoundry Endpoint."

Choose that option and you'll be presented with a dialog asking for the following inputs.

1. Target - An example would be api.cloudfoundry.com or api.vcap.me.
2. Email - The email address you used to register.
3. Password

Once you click Add Zenoss will contact the target and get all of the operationally interesting information that exists. Once it is complete you'll find a new device in the /CloudFoundy device class with the same name as the target you entered into the dialog. Click into this new device to see everything that was discovered.

The following elements are discovered:

• Frameworks
• Runtimes
• App Servers
• System Services
• Provisioned Services
• Apps
• App Instances

The following performance metrics are collected:

• Per-Endpoint (target)
• Limits
• App URIs
• Apps
• Memory
• Services
• Usage
• App URIs
• Apps
• App Instances
• Running App Instances
• Memory
• Services
• Utilization
• App URIs
• Apps
• Memory
• Services
• Per-App
• Resources
• Memory
• Disk
• Usage
• CPU (average across instances)
• Memory
• Disk
• Utilization
• Memory
• Disk
• Instances
• Total
• Running
• Services
• URIs
• Per-App Instance
• Quota
• Memory
• Disk
• Usage
• CPU
• Memory
• Disk
• Utilization
• Memory
• Disk

The following default thresholds are configured:

• Over 99% utilization of..
• Endpoint App URIs
• Endpoint Apps
• Endpoint Memory
• Endpoint Services
• App CPU (average across instances)
• App Memory
• App Disk
• App Instance CPU
• App Instance Memory
• App Instance Disk
• Less than 1 running instance per App

zenpacks.zenoss.cloudfoundry's Issues

No add cloudfoundry endpoint option

After do a fresh install in a amazon apliance the zenoss dow not show the cloudfoundry endpoint option, just add a server or add multiple servers.

My config is:
ubuntu 32bits 10.04 server ami-2cc83145 in a small apliance
zenoss 3.1
cloudfoundry plugin 1.0.1

Error while adding CloudFoundry Endpoint

I am working on getting monitoring working using zenpack specified in https://github.com/zenoss/ZenPacks.zenoss.CloudFoundry.
I watched your youtube video http://www.youtube.com/watch?v=uDUUVTWXCPE

I see the following error while trying to add a CloudFoundy endpoint:
INFO zen.ZenDisc: plugins: zenoss.CloudFoundry
2013-08-16 10:49:24,125 INFO zen.CloudFoundry: Requesting system-wide information
2013-08-16 10:49:24,187 ERROR zen.ZenDisc: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): <class 'urllib2.HTTPError'>: HTTP Error 404: Not Found
]
2013-08-16 10:52:24,231 WARNING zen.ZenDisc: Client XXX.com timeout
2013-08-16 10:52:24,231 INFO zen.ZenDisc: Scan time: 180.12 seconds
2013-08-16 10:52:24,250 INFO zen.ZenDisc: Daemon ZenDisc shutting down
2013-08-16 10:52:25,574 INFO zen.Job: Job ebd55bd0-c04d-4867-8242-c961c566e98b Finished with result 0
2013-08-16 10:52:25,575 INFO zen.Job: Job ebd55bd0-c04d-4867-8242-c961c566e98b finished with result 0

Any idea what could be going wrong?

adding a instance result in a failure

i just installed your plugin and when i try to add a cloud instance i get the following in the log

2012-03-02 15:31:12,514 INFO zen.ZenDisc: Connecting to localhost:8789
2012-03-02 15:31:12,526 INFO zen.ZenDisc: Connected to ZenHub
2012-03-02 15:31:12,575 INFO zen.ZenDisc: Looking for api.cloud.eden.klm.com
2012-03-02 15:31:12,706 INFO zen.ZenDisc: Found IP '172.26.167.181' on device '172.26.167.181'; skipping discovery
2012-03-02 15:31:12,707 INFO zen.ZenDisc: Result: Discovered device api.cloud.eden.klm.com.
2012-03-02 15:31:12,707 INFO zen.ZenDisc: Scan time: 0.00 seconds
2012-03-02 15:31:12,708 INFO zen.ZenDisc: Daemon ZenDisc shutting down

Job completed at 2012-03-02 15:31:13. Result: failure.

and when i go to instance in zenoss i get
TypeError float() argument must be a string or a number