End-to-End Monitoring: Schedules

Updated

End-to-End Monitoring: Schedules

Overview

Use this page to view when monitoring profiles are scheduled to run. A monitoring profile is a configured synthetic check that LoadGen runs against a system under test on a recurring basis; without a consolidated calendar, confirming whether and when a given profile executes would mean checking each profile's configuration individually. This page lays out every profile's scheduled runs on a single weekly grid, by day and hour.

Before anything appears here, a monitoring profile must exist and have a schedule attached, both set up on End-to-End Monitoring: Profiles and Configuration: End-to-End Monitoring: Schedule Definitions. Once a profile is running, its results feed End-to-End Monitoring: Dashboard, and alert triggers configured under Alerting: Triggers evaluate those results as they arrive.

On this page you review a seven-day calendar centered on the current week, move between weeks, and confirm which profiles are due to run in any given hour. The page is read-only: to change what runs or when, use the Manage Schedules link to open the schedule definitions.

Key concepts

  • monitoring profile - A configured synthetic check that LoadGen runs against a system under test on a recurring basis. (related: End-to-End Monitoring: Profiles)
  • schedule - The recurrence rule that determines which days and hours a monitoring profile runs. (related: Configuration: End-to-End Monitoring: Schedule Definitions)

When to use it

  • Confirming exactly when a specific monitoring profile is due to run before a release or maintenance window.
  • Checking for overlapping or back-to-back runs across profiles in the same hour.
  • Verifying a newly created schedule actually appears in the calendar after saving it.
  • Reviewing past weeks to confirm a profile ran at the time it was supposed to.
  • Planning capacity or coordinating infrastructure changes around scheduled run times.

Before you begin

  • At least one monitoring profile exists, created on End-to-End Monitoring: Profiles.
  • The profile has a schedule attached, configured on Configuration: End-to-End Monitoring: Schedule Definitions - profiles without a schedule never appear on this calendar.
  • You have access to the End-to-End Monitoring module to view this page.

Common workflows

Confirm when a monitoring profile is scheduled to run

Persona: Load-test operator checking run timing before a maintenance window

  1. Open Schedules and note the current week's date range shown above the calendar.
    • Expect: The weekly grid loads with the current day's column highlighted and every hour from the start of the day listed down the Time column.
  2. Locate the profile's chip - for example, a profile named svc.lg.crane - in the day column and time slot you expect it to run.
    • Expect: A colored chip in that cell confirms the profile is scheduled there; an empty cell means nothing is scheduled for that profile at that hour.
  3. Select Previous or Next to check the same profile in an earlier or later week.
    • Expect: The grid reloads with that week's date range and chips, letting you compare schedules across weeks.

Verify: The profile's chip appears in the day and hour you expected for the current week; if it's missing everywhere, the profile has no active schedule and needs one added under Manage Schedules.

Steps

Step 1

Open Schedules from the End-to-End Monitoring section of the navigation menu.

Expected result: The weekly calendar loads for the current week (October 5 - October 11, 2026); the Wed 7 column is highlighted as today, and colored chips fill most hourly rows across all seven days.

This is the starting view for confirming when every monitoring profile is due to run before you check results or adjust timing elsewhere.

  • The date range above the grid (October 5 - October 11, 2026) and the bold Wed 7 header show which week and day you're viewing.
  • Each chip (for example LoadGen Demo ...) names the monitoring profile scheduled in that cell; names are truncated and colors aren't explained by an on-screen legend.
  • A Credentials expiring banner may appear over the grid - dismiss it with Close, or resolve the underlying credential on Configuration: Credential Profiles. End-to-End Monitoring: Schedules - step 1

Controls reference

Close

Dismisses the Credentials expiring notification banner shown over the calendar.

When to use: When the banner is covering part of the grid and you've noted the warning.

Side effects: Read-only for this page - hides the banner for the session; it does not reissue the credential or change any schedule data.

Previous

Moves the calendar back one week.

When to use: To review which profiles ran, or were scheduled to run, in a prior week.

Side effects: Read-only - reloads the grid with the prior week's date range and that week's chips.

Next

Moves the calendar forward one week.

When to use: To check upcoming scheduled runs before a maintenance window or release.

Side effects: Read-only - reloads the grid with the following week's date range and chips.

Today

Returns the calendar to the week containing the current date.

When to use: After navigating with Previous or Next, to get back to the current week quickly.

Side effects: Read-only - reloads the grid to the current week.

Retry

Reloads the schedule data after a failed fetch.

When to use: When the calendar shows a 'Failed to load schedules' message instead of the weekly grid.

Side effects: Read-only - re-requests the data; does not change any schedule.

Manage Schedules

Opens the schedule definitions page where recurring run times are created and edited.

When to use: When the calendar shows a profile at the wrong time, shows it missing entirely, or you need to add a new recurring run.

Side effects: Navigates away from the Schedules calendar to Configuration > Schedule Definitions; no data on this page changes.

Verify the result

When the page is working, the weekly grid shows a date range above it and a colored chip in every cell where a monitoring profile is scheduled to run that hour; cells with no scheduled run stay empty. The current day's column header is highlighted so you can immediately locate today's runs. Reading the truncated chip label tells you which profile is scheduled at that day and hour. If a profile you expect to see never appears anywhere in the grid across any week, its schedule either was never saved or was disabled - check it on Manage Schedules. If the grid shows an error message instead of chips, the schedule data failed to load rather than the profile being unscheduled.

Troubleshooting

  • Symptom: the day you need isn't visible in the current view. Fix: select Previous or Next to navigate to the week that contains the date you need, or Today to return to the current week.
  • Symptom: a profile you expect to see never appears in any day's column. Fix: confirm the profile has a schedule attached - follow Manage Schedules to the schedule definitions and check it's enabled there.
  • Symptom: the calendar shows a 'Failed to load schedules' message instead of chips. Fix: select Retry to reload the grid; if it keeps failing, note the error and contact your administrator.
  • Symptom: you can't tell which chip belongs to which profile because names are truncated. Fix: cross-check the chip's color and truncated prefix against the full profile list on End-to-End Monitoring: Profiles.
  • Symptom: the Credentials expiring banner covers part of the calendar grid. Fix: select Close to dismiss it for this session, and reissue the credential on Configuration: Credential Profiles before it expires.
Was this article helpful?
0 out of 0 found this helpful