Configuration: End-to-End Monitoring: Schedule Definitions

Updated

Configuration: End-to-End Monitoring: Schedule Definitions

Overview

Use this page to create and manage the recurring run windows that trigger End-to-End Monitoring checks. A schedule defines which days, what daily time window, which time zone, and how often (the run interval) a monitoring profile should execute, so checks don't have to be started by hand. This turns monitoring into a predictable cadence, for example limiting checks to business hours or running them continuously.

A schedule is only a timing definition: the End-to-End Monitoring profile it drives, created on the End-to-End Monitoring: Profiles page, defines what actually gets tested. Once a profile is attached, it runs on the Days, Time Range, and Interval configured here until the schedule is disabled, deleted, or its optional date range ends. Results of those scheduled runs appear on the End-to-End Monitoring: Dashboard.

On this page you can review every schedule in a sortable table showing its Days, Time Range, Interval, linked Profiles, and Status; create a new schedule; edit or disable an existing one; and delete schedules you no longer need.

Key concepts

  • Schedule - A named run window, made up of active Days, a Daily Time Window, a Time Zone, and a Run Interval, that controls when an End-to-End Monitoring profile executes automatically.
  • Profile - An End-to-End Monitoring profile defines what gets tested; a schedule only controls when it runs and does nothing on its own until a profile is attached to it. (related: End-to-End Monitoring: Profiles)
  • Run Interval - How often, within the schedule's active window, the attached monitoring profile is triggered again.
  • Time Zone - The reference zone the schedule's Daily Time Window is evaluated against, independent of the platform's own display time zone.

When to use it

  • You need End-to-End Monitoring checks to run automatically during business hours instead of around the clock.
  • You want round-the-clock coverage for a critical workflow, similar to the Whole Week Monitor pattern shown in the default schedules.
  • You need to change how frequently a monitoring profile runs, for example lowering the Run Interval to catch issues sooner.
  • You need to pause monitoring temporarily, such as during planned maintenance, without deleting the schedule configuration.
  • You're auditing which schedules exist, whether they're Enabled, and whether a monitoring profile is already attached to them.

Before you begin

  • An End-to-End Monitoring profile exists on the End-to-End Monitoring: Profiles page if you want the schedule to actually drive checks; a schedule with no attached profile is still saved but shows None in the Profiles column and triggers nothing.
  • You know the time zone and daily hours the target system should be monitored in, since the Time Zone field controls how the Daily Time Window is interpreted.
  • Your account has permission to manage End-to-End Monitoring configuration (shown here as the GlobalAdmin role in the current session).

Common workflows

Create a new monitoring schedule

Persona: Load-test operator

  1. Click New Schedule.
    • Expect: The Create Schedule dialog opens with empty Name, Description, Days, Daily Time Window, Time Zone, Date Range, and Run Interval fields, and the Enabled toggle on by default.
  2. Enter a name such as Sagitta month-end batch in Name, select the active Days, set the Daily Time Window and Time Zone, and set the Run Interval.
    • Expect: The dialog reflects the values you entered, ready to save.
  3. Click Create Schedule.
    • Expect: The dialog closes and the new schedule appears as a row in the Schedules table with a green Enabled Status chip and None in the Profiles column.

Verify: The new schedule's row shows the Days, Time Range, and Interval you configured and its Status chip reads Enabled; attach a monitoring profile from the End-to-End Monitoring: Profiles page to replace None with the profile name.

Disable a schedule without deleting it

Persona: Admin

  1. Click the edit pencil icon on the schedule's row.
    • Expect: The dialog opens pre-filled with that schedule's saved Days, Time Range, Time Zone, Interval, and Enabled state.
  2. Turn off the Enabled toggle.
    • Expect: The toggle switches to its off position, marking the schedule for deactivation once saved.
  3. Click Create Schedule to save.
    • Expect: The dialog closes and the row's Status chip no longer reads Enabled, stopping further automatic runs for the profiles it was driving.

Verify: The schedule's Status column no longer shows Enabled, and no new checks trigger from it until you re-enable it the same way.

Steps

Step 1

Open the Schedules page from the End-to-End Monitoring configuration menu.

Expected result: The table loads the existing schedules sorted by Name, showing Days, Time Range, Interval, Profiles, and Status for each row; all three schedules shown are Enabled and show None in Profiles.

This list is where you review existing run windows before creating or editing a schedule for a monitoring profile.

  • New Schedule opens the create dialog; Refresh reloads the list without changing any data.
  • The Profiles column reads None for every row here, meaning no monitoring profile is attached to these schedules yet.
  • Each row's pencil and trash icons under Actions open edit and delete for that schedule only. Configuration: End-to-End Monitoring: Schedule Definitions - step 1

Field reference

Field Purpose Format / Validation Required Default
Name Identifies the schedule in the list. The platform allows duplicate names, so pick something specific enough to tell schedules apart (for example by target system or time window) rather than relying on the list alone. text Yes -
Description A free-text note stored with the schedule; use it to record why the schedule exists or what distinguishes it from a similarly named one. text No -
Days Sets which days of the week the schedule is active. Choosing Weekdays skips Saturday and Sunday runs, useful for business applications not used on weekends; choosing Every day runs checks year-round including weekends for full coverage at the cost of additional runs. day selector Yes -
Daily Time Window Sets the start and end time each active day during which the schedule can trigger checks. A narrow window such as 08:00-18:00 limits monitoring and run volume to business hours; a full-day window such as 00:00-23:59 gives round-the-clock coverage. time range (HH:mm - HH:mm) Yes -
Time Zone Sets which time zone the Daily Time Window is evaluated in. Match it to the monitored system's business hours so the window triggers at the intended local time rather than the platform's own display time zone. time zone selector Yes -
Start Date Optionally bounds the schedule to begin on a specific date; leave it empty to make the schedule active immediately after saving. date No -
End Date Optionally bounds the schedule to stop triggering after this date. Use it for a temporary need, such as a single batch window or event, instead of deleting the schedule manually afterward. date No -
Run Interval Controls how often, within the active window, the schedule triggers the attached monitoring profile. A shorter interval, such as 5 min, detects problems sooner but produces more runs and load on the monitored system; a longer interval, such as 15 min, reduces run volume at the cost of slower issue detection. number + unit (minutes) Yes -
Enabled Turns the schedule on or off without deleting it. Switch it off to pause every check it drives, for example during planned maintenance, and switch it back on to resume at the saved Days, Time Range, and Interval. toggle No Enabled

Controls reference

Refresh

Reloads the schedule list from the server.

When to use: After another admin may have changed schedules, or to confirm a recent save took effect.

Side effects: Read-only: re-fetches the list, no data changes.

New Schedule

Opens the Create Schedule dialog with empty Name, Description, Days, Daily Time Window, Time Zone, Date Range, and Run Interval fields, and the Enabled toggle on by default.

When to use: When you need a new recurring run window for an End-to-End Monitoring profile.

Side effects: Opens a dialog only; no schedule is created until you save it.

Edit

Opens the same dialog, pre-filled with that row's saved Days, Time Range, Time Zone, Interval, Date Range, and Enabled state.

When to use: To change any configured value of an existing schedule.

Side effects: Opens a dialog only; no changes are saved until you confirm.

Delete

Opens a confirmation dialog naming the schedule to remove.

When to use: To permanently remove a schedule you no longer need.

Side effects: Mutating once confirmed: the row is permanently removed and stops triggering any checks it was driving.

Create Schedule

Saves the dialog's field values as a new schedule, or saves edits when the dialog was opened from Edit.

When to use: After filling in Name, Days, Daily Time Window, Time Zone, and Run Interval, or after changing any field on an existing schedule.

Side effects: Mutating: adds a new row to the Schedules table, or updates the existing row's values; the button shows Saving... while the request is in progress.

Cancel

Closes the dialog without saving.

When to use: When New Schedule or Edit was opened by mistake, or you decide not to keep your changes.

Side effects: Read-only: discards any unsaved edits in the dialog.

Delete Schedule confirmation

Confirms the permanent deletion requested from a row's Delete action.

When to use: Only after verifying the confirmation message names the correct schedule.

Side effects: Mutating: permanently deletes the schedule; this cannot be undone.

Column sort headers (Name, Days, Time Range, Interval, Profiles, Status)

Toggles the sort order of the table by that column.

When to use: To group schedules by, for example, Status or Interval instead of the default Name order.

Side effects: Read-only: only changes the row order on screen.

Verify the result

A successfully created or edited schedule appears as its own row in the Schedules table, matching the Days, Time Range, Interval, and Status configured in the dialog. A newly created schedule shows a green Enabled chip in Status and None in Profiles until you attach a monitoring profile from the End-to-End Monitoring: Profiles page. If you disabled a schedule instead, its Status chip no longer reads Enabled and it stops triggering runs. If a row doesn't reflect your change, click Refresh; if it still doesn't match, reopen it with the edit pencil icon and confirm there's no error message in the dialog.

Troubleshooting

  • Symptom: The Profiles column still shows None after creating a schedule. Fix: Attach the schedule to a monitoring profile from the End-to-End Monitoring: Profiles page; this page only defines timing, not which profile uses it.
  • Symptom: Two rows show the same name, such as Business Hours Monitor, and you can't tell which is which. Fix: The Name field doesn't enforce uniqueness; open each row's edit pencil icon to compare its Days, Time Range, and Interval, or rename one for clarity.
  • Symptom: A schedule's Status stays Enabled but checks don't run when expected. Fix: Open the edit pencil icon and check the Time Zone field; the Daily Time Window is evaluated against that saved time zone, not the Times in zone shown in the top header.
  • Symptom: A change made through the edit pencil icon doesn't appear in the table. Fix: Click Refresh to reload the list, and if the row still shows old values, reopen Edit and confirm there's no validation error in the dialog before saving again.
  • Symptom: You want to pause a schedule temporarily but don't want to lose its configuration. Fix: Open it with the edit pencil icon and turn off the Enabled toggle instead of using the trash icon, which deletes it permanently.
Was this article helpful?
0 out of 0 found this helpful