Time zones

Table of contents

Cloud Cruiser must convert collected usage data from its time zone of origin to the server time zone so that data from different geographic locations can be merged.

Setting the time zone

You can set the time zone of origin for a job with the usageTimeZone property of the processInfo bean. To properly support Daylight Savings Time, use a specific time zone ID such as US/Pacific rather than a generic offset such as GMT-0700. If you do not set the usageTimeZone property, usage data is assumed to originate in the server time zone.

For example, for data collected from a source in California you would specify the following:

During the Transformation step, you can also set the time zone for state and shift logs. For example, you can use the stateChangeTimeZone property of ApplyStateChanges to set the time zone for the state change records so that timestamps are properly converted to the same Greenwich Mean Time (GMT) as the usage data:

When adding a shift identifier, you can use the scheduleTimeZone property of AssignShift to set the time zone for the shift schedule records so that start times are properly converted to the same time zone as the usage data.