Cloudera Director Usage Bundles
- The version of the metadata structure
- The complete license key and billing ID for the deployment
- The creation time of the bundle
- A message ID structure, used by Cloudera's metering service for context and sequencing
Cloudera Manager Block
The Cloudera Manager block contains information queried from Cloudera Manager about itself and clusters that it manages.
Initial metadata in the block includes the metadata structure version and the host, port, and API version of Cloudera Manager itself.
- Cluster, service, and role names
- Service and role configurations (redacted) and health statuses
- Cloudera Manager's internal user accounts, with redacted passwords
- Instances' Cloudera Manager host identifiers, private IP addresses, and private host names
- Instances' core counts and memory sizes
Finally, the block includes time series data for the capacity and used capacity of each filesystem associated with the Cloudera Manager instance and with every instance that is part of a cluster. The data covers the five minutes prior to the bundle's creation. See the Cloudera Manager REST API documentation for complete information on the data structures in a time series. Instance private IP addresses and host names are included in the time series data.
Cloudera Director Block
The Cloudera Director block contains information queried from Cloudera Director itself about Cloudera Manager installations and clusters that it manages. For complete information on the data structures described here, consult the Cloudera Director API documentation or explore using the API console included with Cloudera Director, at the /api-console URL.
Initial metadata in the block includes the metadata structure version and the host, port, and API version of Cloudera Director itself. Ensuing details begin with the version of Cloudera Director and the time when the block was created.
- Redacted license and billing ID (which are available unredacted in the usage bundle metadata)
- External Cloudera Manager database templates, if any
- The Cloudera Manager instance template
- The Cloudera Manager version and private IP address
- Details about the instance running Cloudera Manager, including its public and private IP addresses and host names, information specific to the cloud provider such as virtual network and subnet identifiers, its installed software capabilities, and its instance template
- The Cloudera Manager port and administrative username
- The cluster template name and list of services deployed
- External service database templates, if any
- Virtual instance groups and associated instance templates
- Overall cluster health and individual service health checks
- Installed software capabilities of each cluster instance
Cloudera Director is capable of logging usage bundles and heartbeats as they exist immediately before submission to Cloudera's metering service. The logging is disabled by default, but it can be enabled and configured to provide visibility into precisely what Cloudera Director is sending out.
Change the level for each logger to INFO to enable usage logging. To disable usage logging, change the level back to ERROR. After changing the level, restart Cloudera Director so that the change takes effect.
The logging configuration writes the JSON for heartbeats and usage bundles to a dedicated log file. Those comfortable with configuring the Logback logging system can make further changes to have the information written elsewhere. Consult Logback documentation for the options available.
Usage logging increases the demand for file storage on the Cloudera Director instance. Do not enable it for long periods of time, to avoid running out of disk space.