A calendar schema specifies which days should be considered during the aggregation to weekly, monthly, quarterly, or yearly values. You can create your own schemata or edit existing schemata.
Create a calendar schema to ensure that only the periods that are relevant for you are stored in the Central Performance History (CPH). You can, for example, remove weekends or public holidays from the calculation of aggregates.
Setting | Condition |
---|---|
Day, month, year: any(*); Week day: Saturday; Additional restrictions: None |
All days that fall on a Saturday |
Day, month, year: any(*); Week day: Friday; Additional restrictions: Public Holiday Calendar |
All public holidays, in accordance with the public holiday calendar, that fall on a Friday |
Day, month, year, week day: any(*); Additional restrictions: Individual Public Holiday (Carnival Monday)Holiday (Carnival Monday) |
Carnival Monday, irrespective of the date or week day on which the day falls |
Day, month, week day: any(*); Year: 2003; Additional restrictions: Factory Calendar |
All non-working days during the year 2003, in accordance with the factory calendar |
Edit public holiday and factory calendars using transaction SCAL (see Calendar); you can use the selection help to determine the existing public holiday and factory calendars.
Setting | Description |
---|---|
Discard Days Above |
The days defined above are not included in the aggregation or reporting |
Keep Days Above |
The days defined above are included in the aggregation and reporting |
Use Day Schema |
For the days defined above, only the hours that are selected in the corresponding day schema are included in the aggregation and reporting |
If you have specified different operations in different day assignments for single days, the day assignment that is further down the list of assignments is always the one that is active.
Central Performance History of the Monitoring Architecture start page