Editing profiles¶

The Profiles page manages device profiles and their profile checks. It has the tabs Installed, Available (profiles from the Vesana library that are not installed yet) and — with the permission — MIBs (see MIBs).

Who may do what¶

Profiles apply instance-wide — a change affects every tenant that uses the profile. Therefore:

Action	Who
Change an existing profile or its checks, add checks, order and pins, delete a profile, reset a check	Super Admin only
Create, duplicate, import a new profile	permission create profiles (e.g. tenant admin)
Install a profile from the Vesana library	permission create profiles
Apply a profile update from the Vesana library manually	Super Admin only
View, export	permission view profiles

The page only shows edit buttons when they actually work.

List¶

At the top Import and New Profile. Below:

Search across profile name, vendor, description and check names
Dropdowns category and vendor
Filter chips (multiple choice): Agent, SNMP, Own profile (not shipped), Customised (modified), Without checks — plus "Reset filters"

Profiles are listed as rows, grouped by category (display name, "Other" last). Each row shows icon, name, state (Built-in, Customised, Own profile), library origin and "Update available" if any, the number of checks and of devices using the profile. A profile without checks that devices use carries a warning.

A row's actions sit on the right as icons, in the ⋯ menu and on right-click: Update to … (when an update is available, super admin), Add checks, Edit Profile, Duplicate, Export as file, Delete Profile.

Keyboard: ++slash++ focuses the search field, ++n++ creates a new profile.

Profile dialog¶

When creating and editing:

Icon — from Simple symbols or the Icon library (see Icons), already when creating.
Name, Description
Vendor and Category — search fields with suggestions; a new value is taken over with "Add …". Both are optional: without a category the profile ends up under "Other".
How is the device monitored? — operating system and Access to the device: Vesana agent (the host wizard offers the agent installation), SNMP (the wizard asks for SNMP credentials), Needs an address (IP/DNS) (without an address the wizard does not create the device). If a switch does not match the profile's checks, a hint says so and offers Turn on or Turn off.
Device view in host detail — None, Switch (port overview), UPS, NAS (drive bays), Firewall or Internet line.
Assign automatically during discovery — SNMP identifier (sysObjectID) starts with and Device description (sysDescr) contains; * stands for any characters, Enter adds an entry.

For a new profile, "Create and choose checks" creates it and opens the check selection right away.

Adding checks¶

"Add checks" uses the same catalog as "Add check" on the host — several checks at once. Above it you choose where the checks run ("Checked from"):

Choice	Meaning
Agent	Vesana agent on the device; devices without an agent don't get these checks
Collector	collector in the device's network; if a device has no collector, the check automatically runs via the server
Vesana server	the active checker checks itself — always, even if the device has a collector

Agent-capable network checks such as ping can thus also be set to the agent. The switch "Add to new devices automatically" decides whether the check is added to a device automatically when the profile is applied; off means "on request" (marked in the list).

Profile checks¶

A click on a profile row expands its checks. Per check: name, execution (agent / collector / active checker), interval ("Check every"), thresholds as a readable sentence ("Warning from 80 · Critical from 95") and marks such as Reachability or on request.

Quick-edit thresholds: clicking the thresholds opens two small fields right in the row — Enter saves, Esc discards. For check types that do not judge by thresholds this is disabled.

Actions per check (icons, ⋯ menu, right-click): Edit Check, Pin to top, Move up / Move down, Copy to another profile, Reset to shipped state (only for modified shipped checks), Delete Check — devices that already have the check keep it.

Order and pinning¶

The order of the checks in the profile — by dragging or Move up/down — and the pinned checks are the default for every device with this profile: the host detail shows the checks in this order until someone reorders them on the device itself (see Host detail page). Pins travel along in the export and in library profiles.

Editing a check¶

The dialog shows exactly the fields the execution actually reads for each check type — the same field set as when creating and in the host editor. The check type itself cannot be changed.

Section	Content
What is checked?	name, type-specific configuration (for SNMP walks incl. table column, aggregation, reference value, name filter; for HTTP API checks a form), for script checks the script selection and script values; thresholds sit next to the measured value and can only be operated where they take effect
How and how often?	"Checked from" (agent / collector / Vesana server), "Check every", Re-check before alerting (count and interval)
Behaviour	Determines whether the device is reachable (reachability), Add to new devices automatically
Advanced: comparison with an expected value	rarely needed, see Expected values & comparison

If you change a check's reachability, Vesana asks whether devices with their own setting for this check keep it or take over the new one.

Reset¶

"Reset to shipped state" restores the original values of a shipped check; other checks of the profile stay untouched. With "Apply bulk update to existing hosts" the per-device adjustments of this check are removed on all devices as well. Checks without a stored default report a hint instead.

Duplicate¶

Copies a profile with its checks as an own profile: "Generic Linux Server" → "Generic Linux Server (Kopie)", the second time "Generic Linux Server (Kopie) 2".

Export¶

"Export as file" downloads the profile as a JSON file. Credentials in the check configuration (community, password, private key, script passwords) are left out.

Import¶

Import accepts a JSON file or a ZIP with several profiles.

Each profile is imported on its own — a broken one does not take down the rest; the result names success or error per profile.
If the name already exists, the new profile is called "… (Import)", "… (Import 2)" etc.
If the file contains scripts, a dialog asks whether to import with or without scripts. Checks without a script only run once the script exists.
Detection rules (sysObjectID/sysDescr patterns) from the file are only taken over for a Super Admin; for other accounts the profile is imported without automatic assignment.

Deleting a profile¶

Before deleting, the dialog says how many devices lose how many checks (with examples from your tenants). The profile goes to the trash. An unmodified shipped profile cannot be deleted.

API¶

Endpoint	Purpose
`GET /api/v1/profiles/`	List
`GET /api/v1/profiles/{id}`	Detail
`POST /api/v1/profiles/`	New
`PUT /api/v1/profiles/{id}`	Update
`DELETE /api/v1/profiles/{id}`	Delete (trash)
`GET /api/v1/profiles/{id}/usage`	Usage (devices, checks, examples)
`POST /api/v1/profiles/{id}/clone`	Duplicate
`GET /api/v1/profiles/{id}/export`	Export
`POST /api/v1/profiles/import`	Import file/ZIP
`POST /api/v1/profiles/{id}/apply`	Apply to host
`GET` / `POST /api/v1/profiles/{id}/checks`	Read / create profile checks
`PUT` / `DELETE /api/v1/profiles/{id}/checks/{check_id}`	Update / delete profile check
`PUT /api/v1/profiles/{id}/check-order`	Order and pins
`POST /api/v1/profiles/{id}/checks/{check_id}/reset`	Reset shipped check