Interval timing patterns

Interval boundaries are aligned to the logical end of day. It is most likely that the first statistics interval after Gateway daemon initialization will be of a shorter duration than the configured interval length.

The first interval period is shorter than subsequent interval periods if either of the following conditions are met:
  • The Gateway daemon start time does not match one of the interval end times, as shown in the examples in the following tables.
  • You select a figure for an interval period that does not divide equally into 24, for example 5 hours (050000).

Examples of Statistics Interval timings

Interval Statistics timing – Example 1:

The Gateway daemon starts at 5:20 a.m. (052000) and is configured with statint=030000 stateod=000000.

The first Interval is scheduled to end at 6:00 a.m. (060000), and is of 40 minutes duration. This schedule allows subsequent intervals be aligned with the end-of-day event. In this case, statistics are reset and optionally recorded at the following times during the 27 hours following Gateway initialization:
Table 1. Interval Statistics timing – Example 1
Time Event type Interval length HH:MM:SS
05:20:00 Gateway starts Not applicable
06:00:00 Interval reset 00:40:00
09:00:00 Interval reset 03:00:00
12:00:00 Interval reset 03:00:00
15:00:00 Interval reset 03:00:00
18:00:00 Interval reset 03:00:00
21:00:00 Interval reset 03:00:00
00:00:00 End of Day reset 03:00:00
03:00:00 Interval reset 03:00:00
Sequence repeats    

Interval Statistics timing – Example 2:

The Gateway daemon starts at 5:20 a.m. (052000) and is configured for six hour statistics intervals, with logical end of day at 23:59 with statint=060000 stateod=235900.

The first Interval is scheduled to end at 5:59 a.m. (055900), and is of 39 minutes duration. This schedule allows subsequent intervals be aligned with the end-of-day event. In this case, statistics are reset and optionally recorded at the following times during the 30 hours following Gateway initialization:
Table 2. Interval Statistics timing – Example 2
Time Event type Interval length HH:MM:SS
05:20:00 Gateway starts Not applicable
05:59:00 Interval reset 00:39:00
11:59:00 Interval reset 06:00:00
17:59:00 Interval reset 06:00:00
23:59:00 End of Day reset 06:00:00
05:59:00 Interval reset 06:00:00
11:59:00 Interval reset 06:00:00
Sequence repeats    

Interval Statistics timing - Example 3:

The Gateway daemon starts at 5:20 a.m. (052000) and is configured for a 24 hour statistics interval, with logical end of day at 23:59 with statint=240000 stateod=235900.

The first Interval is scheduled to end at 23:59 (235900), and is of 17 hours and 39 minutes duration. This schedule allows subsequent intervals be aligned with the end-of-day event. In this case, statistics are reset and optionally recorded at the following times during the days following Gateway initialization:
Table 3. Interval Statistics timing – Example 3
Time Event type Interval length HH:MM:SS
05:20:00 Gateway starts Not applicable
23:59:00 End of Day reset 17:39:00
23:59:00 End of Day reset 24:00:00
23:59:00 End of Day reset 24:00:00
Sequence repeats