Time policies are user-defined threshold values to be used at different times of the day or week to

account for changing KPI workloads. Time policies accommodate normal variations in usage across

your services and improve the accuracy of KPI and service health scores. For example, if your

organization’s peak activity is during the standard work week, you might create a KPI threshold time

policy that accounts for higher levels of usage during work hours, and lower levels of usage during

off-hours and weekends. The statement that applies when configuring time policies for KPI

thresholds is:

B) They are great if you expect normal behavior at 1:00 to be different than normal behavior at 5:00.

This is true because time policies allow you to define different threshold values for different time

blocks, such as AM/PM, work hours/off hours, weekdays/weekends, and so on. This way, you can

account for the expected variations in your KPI data based on the time of day or week.

The other statements do not apply because:

A) A person can only configure 24 policies, one for each hour of the day. This is not true because you

can configure more than 24 policies using different time block combinations, such as 3 hour block, 2

hour block, 1 hour block, and so on.

C) If a person expects a KPI to change significantly through a cycle on a daily basis, don’t use it. This is

not true because time policies are designed to handle KPIs that change significantly through a cycle

on a daily basis, such as web traffic volume or CPU load percent.

D) It is possible for multiple time policies to overlap. This is not true because you can only have one

active time policy at any given time. When you create a new time policy, the previous time policy is

overwritten and cannot be recovered.

Reference: Create time-based static KPI thresholds in ITSI