 |
Chunjie Zhu |
at Jun 21, 2012 at 1:55 pm
|
⇧ | 
| |
Yes, you are absolutely right.
For CloudFoundry on a single vm through vcap_dev_setup, cloud_controller and health_manager have no index in their configuration files. Actually, for CloudFoundry deployed by bosh, a very awesome cloud service operating framework (https://github.com/cloudfoundry/bosh), both cloud_controller and health_manager get the index configured.
Regards,
Chunjie
----- Original Message -----
From: "Siva" <
[email protected]>
To: "vcap-dev" <
[email protected]>
Sent: Thursday, June 21, 2012 1:07:49 PM
Subject: [vcap-dev] Re: Why does each component message has a index?
Hai,
Collector looks for non-null index to collect metrics.
The config files for services components have the index set (eg "index
=0"). but the config for core components do not have the index set.
Once we set the index in the config files for core components, the
collector sends metric without errors. (eg, cloud_controller.yml,
health_monitor.yml etc)
On Jun 20, 7:07 pm, Chunjie Zhu wrote:Could you please define these component that have no varz supported? Maybe we have something missed.
Regards,
Chunjie
----- Original Message -----
From: "Siva" <
[email protected]>
To: "vcap-dev" <
[email protected]>
Sent: Wednesday, June 20, 2012 6:02:44 PM
Subject: [vcap-dev] Why does each component message has a index?
Hai,
I trying to understand the collector and dashboard for cloudfoundry.
When i started collector, i was able to note that only few component
services get index like mysql and components like DEA and others
doesn't have index. In collector code it seems that varz data are
fetched only when there is a index? So, how do other components gets
monitored?
