Configuration: End-to-End Monitoring: Schedule Definitions
Overview
Use this page to create, edit, and manage monitoring schedules for End-to-End Monitoring profiles. A schedule is a reusable trigger configuration: it sets which days of the week, which daily time window, which time zone, and how often (the run interval) a monitoring profile should execute. Schedules let you confine monitoring to business hours, run it continuously, or pause it entirely, instead of running checks manually or around the clock.
Before you build a schedule, the End-to-End Monitoring profiles it will trigger are created on the End-to-End Monitoring: Profiles page; a schedule only produces monitoring runs once a profile is attached to it. Once a schedule is enabled, the runs it triggers feed results into the End-to-End Monitoring: Dashboard, where you can see whether checks are passing or failing during the windows you defined here.
This page lists every schedule with its Days, Time Range, Interval, number of attached Profiles, and Status. From here you can create a new schedule, edit an existing one's days, time window, time zone, date range, or interval, enable or disable it, or delete it entirely.
Key concepts
- schedule - A reusable configuration of days, a daily time window, a time zone, and a run interval that controls when End-to-End Monitoring profiles execute. (related: End-to-End Monitoring: Profiles)
- profile - An End-to-End Monitoring profile is the recorded monitoring scenario that a schedule triggers; the Profiles column shows how many are attached to each schedule. (related: End-to-End Monitoring: Profiles)
- Run Interval - How often, within a schedule's active time window, it triggers a monitoring run.
- Time Zone - The time zone used to interpret a schedule's Daily Time Window and Days.
When to use it
- You need End-to-End Monitoring profiles to run only during certain hours, such as business hours, instead of continuously.
- You want to change how frequently a monitoring profile checks a system by adjusting its schedule's Run Interval.
- You need different monitoring coverage on weekdays versus weekends or every day.
- You need to pause monitoring for a period, for example during planned maintenance, without deleting the schedule's configuration.
- You're setting up a new End-to-End Monitoring profile and need a schedule to attach it to.
Before you begin
- Know which Days, Daily Time Window, and Time Zone you want the schedule to cover before opening the create dialog.
- Decide the Run Interval you need: shorter intervals increase monitoring frequency and load, longer intervals reduce both.
- If the schedule is for an existing monitoring scenario, create the End-to-End Monitoring profile first on End-to-End Monitoring: Profiles so you can attach it.
- Have permission to configure End-to-End Monitoring settings; this page lives under Configuration.
Common workflows
Create a new monitoring schedule
Persona: Load-test admin
- Select New Schedule in the page header.
- 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.
- Enter a Name, select the Days and Daily Time Window, choose a Time Zone, and set the Run Interval.
- Expect: Each field reflects the value you entered or selected.
- Select Create Schedule.
- Expect: The dialog closes and the new schedule appears as a row in the list with Status Enabled and Profiles showing None.
Verify: The new schedule appears in the list with the Days, Time Range, and Interval you configured, and a green Enabled status.
Pause a schedule without deleting it
Persona: Monitoring operator
- Select the pencil Edit icon on the schedule row you want to pause.
- Expect: The dialog opens pre-filled with that schedule's current Name, Days, Daily Time Window, Time Zone, Date Range, Run Interval, and the Enabled toggle on.
- Turn off the Enabled toggle.
- Expect: The toggle switches to its off position; the other fields keep their existing values.
- Select Create Schedule to save.
- Expect: The dialog closes and the schedule's Status column changes from Enabled to Disabled.
Verify: The row's Status column no longer shows the green Enabled pill, and any profile attached to that schedule stops running until you re-enable it.
Steps
Step 1
Open Schedules from Configuration: End-to-End Monitoring.
Expected result: The list of existing monitoring schedules loads, showing each schedule's Name, Days, Time Range, Interval, Profiles, and Status; a Credentials expiring notification appears in the top-right reporting that a token used by monitoring profiles expires in 4 days.
This list is the starting point for creating, editing, or disabling the schedules that trigger End-to-End Monitoring profiles.
- The Name column header shows an active ascending sort arrow.
- Each row's Status shows a green Enabled pill.
- The Credentials expiring banner includes a close (X) icon in its top-right corner.
Step 2
Select the close (X) icon on the Credentials expiring notification.
Expected result: The banner disappears, and the page header now shows the Refresh and New Schedule buttons that the banner had been covering; the schedule list itself is unchanged.
Dismissing the banner gives you access to the New Schedule button needed to create additional schedules.
- Refresh reloads the schedule list.
-
New Schedule opens the create-schedule dialog.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Name | Identifies the schedule in the list and wherever it's referenced; choose a name that reflects its purpose, such as a business-hours window versus a full-week window. | free text | Yes | - |
| Description | Optional free-text notes about what the schedule is for; has no effect on when the schedule runs. | free text | No | - |
| Days | Controls which days of the week the schedule is active; choose a limited set such as weekdays only to monitor during business operation, or every day for continuous coverage. | day selection | Yes | - |
| Daily Time Window | Sets the start and end time the schedule is active on each active day; a narrower window such as 08:00 - 18:00 limits monitoring to specific hours, while a full 00:00 - 23:59 window gives around-the-clock coverage. | start time - end time | Yes | - |
| Time Zone | Sets the time zone used to interpret the Daily Time Window and Days; pick the time zone of the business hours or systems you're monitoring so the window lines up with local operating hours. | time zone selector | Yes | - |
| Start Date | Optional date from which the schedule becomes active; leave it blank to make the schedule active immediately once enabled. | date | No | - |
| End Date | Optional date after which the schedule stops triggering runs, even if still Enabled; use it for temporary monitoring windows around a single event or migration. | date | No | - |
| Run Interval | Sets how often, within the active Daily Time Window, the schedule triggers a monitoring run; lower values check more frequently and surface issues sooner but increase load on agents and monitoring data volume, higher values reduce both at the cost of slower detection. | duration in minutes | Yes | - |
| Enabled | Toggles whether the schedule is active; turn it off to pause monitoring runs for every profile attached to it without deleting the schedule's configuration. | toggle | No | on |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Name | Shows the schedule's name as set when it was created. | Select the column header to sort the list alphabetically by name; select again to reverse the order. |
| Days | Shows which days the schedule is active. | Weekdays or Every day tells you the active days configured for the schedule; select the header to sort the list by this value. |
| Time Range | Shows the daily start-end time and time zone configured for the schedule. | Read the two times as the active window each day, and the trailing name as the time zone they're interpreted in. |
| Interval | Shows how often the schedule triggers a run within its active window. | A smaller value means more frequent runs; compare across schedules to see which one monitors most aggressively. |
| Profiles | Shows how many End-to-End Monitoring profiles are attached to the schedule. | None means no profile currently runs on this schedule; attach one from End-to-End Monitoring: Profiles for the schedule to trigger any monitoring. |
| Status | Shows whether the schedule is currently active. | A green Enabled pill means the schedule runs its attached profiles on its configured Days and Time Range; disable it from the edit dialog to pause runs without deleting the schedule. |
| Actions | Provides per-row edit and delete controls. | Select the pencil icon to edit the schedule, or the trash icon to delete it. |
Controls reference
Refresh
Reloads the schedule list from the server.
When to use: After another user or process may have changed schedules, or if the list looks out of date.
Side effects: Read-only: re-fetches and redisplays the list; does not change any schedule.
New Schedule
Opens the create-schedule dialog with empty Name, Description, Days, Daily Time Window, Time Zone, and Date Range and Run Interval fields, and the Enabled toggle on.
When to use: When you need a new trigger configuration for one or more End-to-End Monitoring profiles.
Side effects: Opening the dialog changes nothing by itself; selecting Create Schedule inside it adds a new schedule to the list.
Edit
Opens the same dialog as New Schedule, pre-filled with the selected schedule's current settings.
When to use: To change a schedule's days, time window, time zone, date range, interval, or enabled state.
Side effects: Mutating once saved: the schedule's settings are overwritten with the values in the dialog.
Delete
Opens a confirmation dialog naming the schedule, then removes it if confirmed.
When to use: When a schedule is no longer needed, for example after retiring the profiles it was meant to trigger.
Side effects: Mutating: permanently removes the schedule and stops any monitoring runs it was triggering; cannot be undone.
Close (notification)
Dismisses the Credentials expiring banner.
When to use: When you've read the warning, or want to access the Refresh and New Schedule buttons it covers.
Side effects: Read-only: hides the notification; does not reissue or otherwise affect the underlying credential.
Create Schedule
Saves the values entered in the create/edit dialog as a new or updated schedule.
When to use: After filling in Name, Days, Daily Time Window, Time Zone, and Run Interval for a new schedule, or after changing any of these for an existing one.
Side effects: Mutating: adds a new row to the list (create) or updates the existing row's values (edit); shows a brief saving state while the request completes.
Cancel
Closes the create/edit dialog without saving.
When to use: When you opened the dialog by mistake or decide not to keep your changes.
Side effects: Read-only: discards any values entered in the dialog; the schedule list is unchanged.
Verify the result
A successfully configured schedule shows up as a row in the list with the Days, Time Range, Interval, and Status you set, and the Profiles column reflects any monitoring profile you've attached to it. A green Enabled pill confirms the schedule will trigger runs during its configured window; a schedule you've paused shows Disabled instead. If a new or edited schedule doesn't appear after saving, select Refresh to confirm the list is current before assuming the save failed.
Troubleshooting
- Symptom: The Refresh and New Schedule buttons aren't visible in the page header. Fix: A notification such as Credentials expiring can overlay the header toolbar; select its close (X) icon to dismiss it and reveal the buttons underneath.
- Symptom: A schedule shows Enabled but its attached profile never runs outside certain hours. Fix: Runs only happen during the configured Daily Time Window and on the selected Days, interpreted in the schedule's Time Zone; confirm these settings match when you expect the profile to run.
- Symptom: The Profiles column shows None for a schedule you expect to be driving monitoring runs. Fix: No profile is currently attached to that schedule; attach it from End-to-End Monitoring: Profiles.
- Symptom: You deleted the wrong schedule. Fix: Deletion is confirmed in a separate dialog before it takes effect; select Cancel there if you're not certain, since confirming immediately stops monitoring for any profile attached to that schedule.
- Symptom: Monitoring runs more or less often than expected. Fix: Adjust the Run Interval value: lower it for more frequent checks, raise it to reduce load on agents and monitoring data volume.
Related articles
- Prerequisite: End-to-End Monitoring: Profiles - profiles must exist before a schedule can trigger any monitoring runs
- Next step: End-to-End Monitoring: Dashboard - view the results of the runs a schedule triggers
- See also: Configuration: Credential Profiles - the page's expiring-credentials notification points here to reissue the token
- See also: Configuration: End-to-End Monitoring: Platform Agents - agents execute the monitoring runs a schedule triggers