The reporting function automatically compensates for changes in the length of a day due to the start or the expiry of Daylight Saving Time (DST). This adjustment is necessary when the beginning or end of DST occurs during a period when you are collecting data for a report.
To compensate for DST changes, the calculation mechanism adjusts the time at which data collection starts and the manner in which data is presented in the resultant graph of the data points. The collection period remains the length that you specify.
You are not required to make any modifications to your configuration to enable DST compensation.
The following examples use the U.S. dates and times for making DST adjustments. All examples are based on a 24-hour data collection period ending at 12:00, using a 24-hour clock. Data points are recorded hourly.
Normal data collection period (no DST)
For a normal data collection period, DST is not a factor. Data collection for this example takes place between June 1 and June 2.
The first data point is recorded at 13:00 on June 1. The 24-hour data collection period ends at 12:00 on June 2.
The following table shows the times at which data points are recorded.
Data collection for normal period
| Date | Collection time | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6/1 | 13.00 | 14.00 | 15.00 | 16.00 | 17.00 | 18.00 | 19.00 | 20.00 | 21.00 | 22.00 | 23.00 | 00.00 |
| 6/2 | 1:00 | 2:00 | 3:00 | 4:00 | 5:00 | 6:00 | 7:00 | 8:00 | 9:00 | 10:00 | 11:00 | 12:00 |
DST begins during data collection period
This example shows a 24-hour data collection period that includes the beginning of DST, when clocks are set forward by 1 hour.
Due to DST, April 3 is only 23 hours long. The reporting mechanism compensates by beginning the collection period at 11:00 on April 3, not 12:00, as is it would on a regular day. The 24-hour data collection period ends at 12:00 on April 4.
The following table shows the times at which data points are recorded. The first data point is taken at 12:00 on April 3, covering the period from 11:00 to 12:00. The last data point is recorded at 12:00 on April 4. If clocks are reset at 2:00 on April 4, the 2:00 data point is not included in the collection.
Data collection for period that includes beginning of DST
| Date | Collection time | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 4/3 | 12.00 | 13.00 | 14.00 | 15.00 | 16.00 | 17.00 | 18.00 | 19.00 | 20.00 | 21.00 | 22.00 | 23.00 | 00.00 |
| 4/4 | 1.00 | 3:00 | 4:00 | 5:00 | 6:00 | 7:00 | 8:00 | 9:00 | 10:00 | 11:00 | 12:00 | ||
DST ends during data collection period
This example shows a 24-hour data collection period that includes the end of DST, when clocks are set back by 1 hour.
Due to DST, October 31 is 25 hours long. The reporting mechanism compensates by beginning the collection period at 13:00 on October 30, not 12:00, as is it would on a regular day. The 24-hour data collection period ends at 12:00 on October 31.
The following table shows the times at which data points are recorded. The first data point is taken at 14:00 on October 30, covering the period from 13:00 to 14:00. The last data point is recorded at 12:00 on October 31. If clocks are reset at 2:00 on October 31, the 2:00 data point appears twice in the graph.
Data collection for period that includes end of DST
| Date | Data points by hour | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 10/30 | 14.00 | 15.00 | 16.00 | 17.00 | 18.00 | 19.00 | 20.00 | 21.00 | 22.00 | 23.00 | 00.00 | ||
| 10/31 | 1.00 | 2.00 | 2.00 | 3:00 | 4:00 | 5:00 | 6:00 | 7:00 | 8:00 | 9:00 | 10:00 | 11:00 | 12:00 |
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks