End-to-End Monitoring: Schedules
Overview
Use this page to view the weekly schedule of monitoring profile runs. A monitoring profile defines what gets checked during a monitoring run, and a schedule determines when that profile executes. This calendar answers something neither of those pages shows on its own: at a given hour on a given day, which profile is actually running. Without it, confirming monitoring coverage would mean checking every schedule definition by hand.
The grid depends on two things being configured first: at least one monitoring profile, created on End-to-End Monitoring: Profiles, and at least one schedule definition, created on Configuration: End-to-End Monitoring: Schedule Definitions, that assigns that profile to specific hours and days. Once a run executes on schedule, its results surface on End-to-End Monitoring: Dashboard.
This page itself shows a seven-day grid with one row per hour and a colored chip in each occupied cell naming the scheduled profile. You can step the view backward or forward one week at a time, jump back to the current week, and tell weekend days apart by their header color.
Key concepts
- monitoring profile - A saved monitoring configuration that defines what a monitoring run checks. (related: End-to-End Monitoring: Profiles)
- schedule - A time-based rule that assigns a monitoring profile to run during specific hours and days of the week. (related: Configuration: End-to-End Monitoring: Schedule Definitions)
When to use it
- Confirm which monitoring profile is scheduled to run at a specific hour before investigating a gap in monitoring data.
- Check for overlapping schedules where two profiles are both assigned to the same day and hour.
- Verify that a newly created schedule definition appears on the calendar at the expected time.
- Review weekday versus weekend monitoring coverage before an on-call handover.
- Step back to a past week or forward to a future week to audit historical or upcoming monitoring coverage.
Before you begin
- At least one monitoring profile must exist, created on End-to-End Monitoring: Profiles.
- At least one schedule definition must exist, created on Configuration: End-to-End Monitoring: Schedule Definitions, that assigns that profile to run times.
- Until a schedule definition exists for a profile, no colored chip for it appears anywhere on this calendar.
Common workflows
Check which monitoring profile is scheduled for a specific day and hour
Persona: load-test operator
- Locate the row for the hour you want to check in the Time column.
- Expect: You see the hour label, for example 08:00, with one cell per day to its right.
- Read the colored chip in the column for the day you want to check.
- Expect: The chip text names the monitoring profile scheduled for that hour, truncated with an ellipsis if the name is long.
- Select Next or Previous if the day falls outside the displayed week.
- Expect: The date-range heading above the grid updates and the grid reloads with that week's entries.
Verify: The date-range heading matches the week you intended to check, and the chip in the target hour and day cell names the expected monitoring profile.
Audit monitoring coverage across a past or upcoming week
Persona: admin
- Select Next to move to the following week, or Previous for an earlier week.
- Expect: The date-range heading updates to the new Monday-through-Sunday range and the grid reloads with that week's chips.
- Scan each day column for hour rows with no colored chip.
- Expect: Empty cells stand out against the surrounding hours that do contain chips.
- Select Today to return to the current week.
- Expect: The heading and grid reset to the week containing today's date.
Steps
Step 1
Open the Monitoring Schedules page.
Expected result: The calendar loads showing the current week (October 19 - October 25, 2026) with one row per hour and one column per day; each occupied time slot shows a colored chip naming the monitoring profile scheduled to run then.
This is the starting view for checking what monitoring coverage is scheduled before you investigate gaps or conflicts.
- The date-range heading above the grid names the week currently displayed.
- Sat and Sun column headers are shown in a different color to mark weekend days.
- Chip color groups entries by monitoring profile, so profiles running on different schedules are easy to tell apart at a glance.
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Time | Identifies the hour-of-day row you are reading across the grid. | Each row is one hour; any profile scheduled to start in that hour shows as a chip in the day columns to the right of it. |
| Day column (Mon through Sun) | Shows, for the date in the column heading, which monitoring profile is scheduled to run in each hour row. | An empty cell means no profile is scheduled for that hour and day; a chip's color groups entries by profile, and the Sat and Sun headers are shown in a different color to mark weekend days. |
Controls reference
Previous
Moves the calendar back one week.
When to use: When you need to check monitoring coverage for a week before the one currently displayed.
Side effects: Read-only: reloads the grid and the date-range heading with the prior week's schedule data, no stored data changes.
Today
Returns the calendar to the week containing the current date.
When to use: After stepping through other weeks, to get back to the present week quickly.
Side effects: Read-only: reloads the grid and heading to the current week.
Next
Moves the calendar forward one week.
When to use: When you need to check what monitoring coverage is scheduled for an upcoming week.
Side effects: Read-only: reloads the grid and the date-range heading with the following week's schedule data.
Retry
Reloads the week's schedule data after a failed load.
When to use: When a Failed to load schedules message appears instead of the grid.
Side effects: Read-only in terms of stored data: it re-attempts the data fetch for the currently selected week.
Manage Schedules
Navigates to the page where schedule definitions are created and edited.
When to use: When the calendar has no entries for a profile you expect to see, or you need to add a new schedule.
Side effects: Navigation only; it does not change anything on this page itself.
Verify the result
The weekly grid loads with the current date range in the heading and colored chips filling the hour rows for days that have scheduled monitoring runs. Each chip names the monitoring profile assigned to that hour, and different profiles use different chip colors so you can tell them apart at a glance. An empty cell means no profile is scheduled to run in that hour for that day. If the grid shows no chips anywhere, or a Failed to load schedules message appears instead, check Configuration: End-to-End Monitoring: Schedule Definitions to confirm a schedule actually exists. Weekend columns (Sat and Sun) are marked with a different header color, which is the first thing to check when confirming off-hours coverage.
Troubleshooting
- Symptom: A cell stays empty for an hour and day you expected a monitoring profile to run. Fix: Check Configuration: End-to-End Monitoring: Schedule Definitions to confirm a schedule definition actually assigns a profile to that hour and day; the calendar only shows runs that have a matching schedule.
- Symptom: The chip text is truncated and you cannot tell which monitoring profile it names. Fix: Cross-check the chip's color and time slot against the profile names on End-to-End Monitoring: Profiles to identify the full name.
- Symptom: A Failed to load schedules message appears instead of the grid. Fix: Select Retry to reload the week's data; if it fails again, revisit the page after a short wait.
- Symptom: Selecting Previous, Today, or Next does not appear to change anything. Fix: Check the date-range heading; it confirms which week is actually displayed and may already match the target week.
- Symptom: No chips appear anywhere on the calendar for any week. Fix: No schedule definitions exist yet; create one from Configuration: End-to-End Monitoring: Schedule Definitions after confirming a monitoring profile exists on End-to-End Monitoring: Profiles, or select Manage Schedules if shown.
Related articles
- Prerequisite: End-to-End Monitoring: Profiles - a monitoring profile must exist before it can appear on this schedule
- Prerequisite: Configuration: End-to-End Monitoring: Schedule Definitions - schedule definitions determine which hours and days a profile runs, driving everything this calendar shows
- Next step: End-to-End Monitoring: Dashboard - shows the results of the monitoring runs this calendar schedules
- See also: Configuration: End-to-End Monitoring: Platform Agents - agents execute the scheduled monitoring runs shown here