Click buttons below to edit the alert schedule lookup files.
Note: this requires the Lookup File Editor App for Splunk Enterprise

Lookup Files Help

• schedule_id: can be anything you want it to be as long as it consistent through all of the lookup files. This is the "primary key" which drives all of the functionality. Note: The included default lookups use contry codes because that was what worked for the original use case this was developed for.
• schedule_description: is a user friendly name for the schedule. This does not drive any functionality and is essentially optional
• schedule_timezone: is the timezone (format %Z) that will be used to specify times when configuring the schedule. This will be used to translate the "local" time of the user running the alert search to the one specified for the schedule. This allows the schedules to be configured using the local time of where the schedule originates.

• schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
• calendar_day_of_week: numeric day of the week 0-6 corresponds to Sunday-Saturday. If there are multiple regular work periods on a day (e.g. Tokyo Stock Exchange), this can be supported by including a second row for the corresponding day.
• start_time: start time of the regualr work day period entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
• end_time: end time of the regualr work day period entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)

• schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
• holiday_description is a user friendly description of the holiday. This does not drive any functionality and is essentially optional
• holiday_date: specific date (format %d/%m/%y) the holiday falls on
• start_time: start time of the holiday entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
• end_time: end time of the holiday entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)

• schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
• mw_description: is a user friendly description of the maintenance window. This does not drive any functionality and is essentially optional
• start_time: start date and time of the maintenance window (format %d/%m/%y %H:%M) in the schedule's Timezone (specified in the schedules.csv)
• end_time: end date and time of the maintenance window (format %d/%m/%y %H:%M) in the schedule's Timezone (specified in the schedules.csv)