Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Cloud Director data collector fails to process some of the chargeback events in vCloud Director

Details

The Cloud Director data collector fails to process some of the vCenter Chargeback related events in your vCloud Director setup, if the corresponding parent event is already purged. By default, vCloud Director purges the chargeback event history after 365 days. For example, let us consider you have created an org in vCloud Director on 01-July-2010. You add an org vDC to this org on 10-September-2011. The org vDC event is not processed by the Cloud Director data collector as the corresponding create org event is more than a year old and, therefore, purged. Similarly, if you create a vApp in an org vDC that is more than a year old, the corresponding create vApp event might not be processed by the Cloud Director data collector.

The symptoms for this issue includes:

  • Changes to the org in your vCloud Director setup is not reflected in the corresponding hierarchy in vCenter Chargeback.
  • The Cloud Director Data Collector log include multiple entries related to failed events.

Solution

The workaround is to modify the time period for which the chargeback events must be kept. To modify this time period value, perform the following tasks:

  1. Log in to the vCloud Director Database.
  2. Run the following query:
    UPDATE config SET VALUE=1096 WHERE cat='Chargeback' AND name='ChargebackEventsKeepDays';

In addition to increasing the time period for which the chargeback events must be kept, you can also perform the following tasks to ensure that unprocessed events are processed by the Cloud Director data collector:

  • Increase the value of the Unprocessed VMware Cloud Director chargeback event life time property of the Cloud Director data collector. In releases prior to vCenter Chargeback Manager 2.0, the default value is 86400 seconds (24 hours). Starting from vCenter Chargeback Manager 2.0, the default value is 864000 seconds (10 days).
  • Install and run more than one instance of the vCenter Chargeback data collector, to reduce the probability of missing any updates to the vCenter Server.

The issue of vCloud Director events not getting processed because of parents events getting purged after 365 days is fixed in the vCenter Chargeback 1.6.2 release for all entity types except network entities.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
KB: