End-to-End Monitoring: Profiles

Overview

Use this page to view, enable, and manage your end-to-end monitoring profiles. A monitoring profile is a saved configuration that tells one or more monitoring agents what to check on a specific target technology, such as a Citrix farm or a web application, and whether that checking is currently turned on. Without a profile, an agent has nothing to run; this page is where every configured profile is listed alongside how much of your monitoring agent license it consumes.

Before you add a profile here, the target technology it monitors and any credentials it needs must already exist, with credentials created on Configuration: Credential Profiles. Once a profile is created and enabled, it draws agents from your license, its checks run on the cadence set on End-to-End Monitoring: Schedules, and its results surface on End-to-End Monitoring: Dashboard.

From this page you can create a new profile, open an existing one to edit or inspect it, enable or disable it without deleting it, delete profiles you no longer need, and refresh the list and license summary to confirm you are looking at current data.

Key concepts

• monitoring profile - A saved configuration that defines what a monitoring agent checks on a target technology, such as a Citrix farm or a web application, and whether that checking is enabled. (related: End-to-End Monitoring: Dashboard)
• monitoring agent - The worker that executes a profile's checks against its target. Each enabled profile assigns one or more agents, and those agents count against your license limit. (related: Configuration: End-to-End Monitoring: Platform Agents)
• credential profile - A stored set of authentication details, such as a bearer token, that a monitoring profile uses to sign in to its target system. (related: Configuration: Credential Profiles)
• monitoring agent license - The total number of monitoring agents your account is entitled to run at once. The banner on this page shows this total and how many agents are currently in use. (related: Infrastructure: Licensing)

When to use it

• You need to see all configured end-to-end monitoring profiles and their enabled or disabled state at a glance.
• You are about to create a new profile and need to check whether your license has spare agent capacity first.
• A profile needs to be paused temporarily, for example during planned maintenance on its target, without deleting its configuration.
• A credential used by one of your profiles is expiring and you need to confirm which profile is affected before it stops collecting data.
• You are retiring a target and need to delete the profile that was monitoring it to free up license capacity.
• You want to confirm that a change made elsewhere (a new schedule, an edited credential) is reflected on the profile list.

Before you begin

• Know which target technology you want to monitor (for example a Citrix environment or a web application) and have its connection details ready.
• Create or confirm a credential profile on Configuration: Credential Profiles if the target requires authentication.
• Check the license banner at the top of this page for spare monitoring agent capacity before creating or enabling another profile.

Common workflows

Review current profiles and refresh after a change

Persona: Load-test operator checking monitoring coverage

1. Open the Monitoring Profiles page.
   • Expect: The page loads showing each configured profile as a card, for example Citrix Infrastructure Health and LoadGen Demo Monitoring, each with its technology badge, agent count, and last-updated date, plus a banner stating your total licensed monitoring agents and how many are in use.
2. Select Refresh.
   • Expect: The cards and the license banner reload from the server, and any stale credential-expiring notice clears.

Verify: The Updated date on each card and the agents-in-use count in the banner match the latest saved state, confirming you are viewing current data rather than a cached list.

Create a new monitoring profile within your license

Persona: Admin adding monitoring for a new target

1. Check the license banner for spare agent capacity.
   • Expect: You see your total licensed monitoring agents versus how many are currently in use across active profiles.
2. Select New Profile.
   • Expect: The profile creation wizard opens for you to define the target technology, credentials, and schedule for the new profile.
3. Complete the wizard and save.
   • Expect: A new card appears in the grid with the chosen name and technology badge, and today's date as its Updated value.

Verify: The new profile's card appears in the grid and the banner's agents-in-use count increases to reflect the agents it now consumes.

Delete a monitoring profile you no longer need

Persona: Operator decommissioning a retired target

1. Select the Delete icon on the profile's card.
   • Expect: A Delete Profile confirmation dialog opens, naming the profile you selected.
2. Confirm the deletion in the dialog.
   • Expect: The dialog closes and the profile's card is removed from the grid.

Verify: The deleted profile's name no longer appears among the cards, and the banner's active-profile and agents-in-use counts drop accordingly.

Steps

Step 1

Open the Profiles page.

Expected result: The Monitoring Profiles page loads showing your existing profiles as cards, here Citrix Infrastructure Health and LoadGen Demo Monitoring, each with a technology badge, agent count, and last-updated date; a banner reports your license allows 5 monitoring agents, and a notice warns that a credential token expires in 4 days.

This gives you a starting inventory of what is already being monitored and whether you are near your license limit before you create or change anything.

• The Citrix Infrastructure Health and LoadGen Demo Monitoring cards show the Citrix and Web technology badges.
• The license banner reads Your license allows a total of 5 monitoring agents.
• The Credentials expiring notice names the affected credential and where to reissue it, under Configuration → Credential Profiles.

Step 2

Select Refresh.

Expected result: The profile cards and license banner reload; with the credential-expiring notice cleared, the full header toolbar, Refresh and New Profile, and each card's Edit, View, Delete, and Enabled toggle are clearly visible.

Refreshing confirms you are looking at the current profile list and license usage rather than a stale snapshot.

• Refresh sits in the header next to New Profile.
• The round indicator in the top right of each card is the Enabled toggle.
• The banner still reads 0 agents in use across 0 active profile(s).

Field reference

Controls reference

Refresh

Reloads the profile cards and the license/agent summary from the server.

When to use: After creating, editing, or disabling a profile elsewhere, or after a credential change, to confirm this page reflects the current state.

Side effects: Read-only: re-fetches data without changing any profile.

New Profile

Opens the profile creation wizard for configuring a new end-to-end monitoring profile.

When to use: When you need to begin monitoring a new target, for example svc.lg.crane, and the license banner shows spare agent capacity.

Side effects: Mutating only once the wizard is completed and saved; opening the wizard alone creates nothing.

Create Profile

The empty-state equivalent of New Profile, shown under the "No Monitoring Profiles" heading when no profiles exist yet.

When to use: When this is the first profile you are creating for the account.

Side effects: Mutating only once the wizard is completed and saved.

Edit

Opens the selected profile in the edit wizard, pre-filled with its current configuration.

When to use: To change what a profile monitors, its target details, or its schedule.

Side effects: Mutating only once changes are saved inside the wizard. Not available on a profile whose target technology this build does not recognize; that profile shows an Unsupported badge instead.

View

Opens the selected profile in a read-only detail view.

When to use: To inspect a profile's configuration without risking a change to it.

Side effects: Read-only.

Delete

Opens a Delete Profile confirmation dialog for the selected profile.

When to use: When a monitoring profile is no longer needed and you want to free the agent capacity it holds.

Side effects: Destructive once confirmed: permanently removes the profile and its card from the grid.

Enabled toggle

The round indicator in the top right of each profile card; switches that single profile on or off.

When to use: To pause monitoring temporarily, for example during target maintenance, or to free agent capacity without deleting the profile.

Side effects: Mutating: can fail with "Couldn't update this profile's status. Please try again." if, for example, you try to enable a profile whose agents have no workload assigned.

Verify the result

On Monitoring Profiles, each configured profile appears as its own card showing its name, technology badge such as Citrix or Web, description, assigned agent count, Enabled toggle, and last-updated date. The banner at the top always states your total licensed monitoring agents and how many are currently in use across active profiles. If you just enabled, edited, or deleted a profile, check that the specific card's toggle state, description, or presence in the grid matches what you expect, and that the agents-in-use count changed accordingly. If a profile you just edited still shows its old values, select Refresh to force the page to reload from the server. If no cards appear at all, no profile has been created yet and the page shows a No Monitoring Profiles message with a Create Profile action instead.

Troubleshooting

• Symptom: Enabling a profile fails with "Couldn't update this profile's status. Please try again." Fix: Check that the profile has a monitoring workload assigned to its agents; a profile with no workload configured cannot be turned on.
• Symptom: A Credentials expiring notice keeps appearing at the top of the page. Fix: Reissue the named credential on Configuration: Credential Profiles before it expires; a profile using an expired credential will stop collecting data even while marked Enabled.
• Symptom: New Profile does nothing useful because you cannot add another profile. Fix: Check the license banner; if agents in use already equals your total licensed monitoring agents, disable or delete an existing profile, or increase your license, before adding another.
• Symptom: A profile card shows an Unsupported badge with no Edit icon. Fix: This profile targets a technology the current build does not recognize because the API is newer than the frontend; you can still enable, disable, or delete it, but editing requires an updated frontend.
• Symptom: The agents-in-use count in the banner does not match the number shown on an individual card. Fix: The banner counts agents across enabled profiles only, while a card's own agent count includes agents assigned even when the profile is disabled; check each card's Enabled toggle to reconcile the totals.

Related articles

• Next step: End-to-End Monitoring: Schedules - set when an enabled profile's checks run
• Next step: End-to-End Monitoring: Dashboard - view the monitoring results collected by profiles configured here
• Prerequisite: Configuration: Credential Profiles - create or reissue the credentials a profile authenticates with
• See also: Configuration: End-to-End Monitoring: Platform Agents - see the monitoring agents counted against your license here
• See also: Infrastructure: Licensing - check or change the monitoring agent limit shown in the banner