CT-Ops

Agent Defaults

Global CT-Ops settings for default host data collection and default host tags.

The Agent Defaults settings page controls the default collection and tag state for newly enrolled or newly approved hosts. Open it from Settings -> Agents -> Host defaults at /settings/agents/defaults.

These settings affect host management because a host’s Data Collection card falls back to the instance defaults when the host has no host-specific collection settings, and newly approved hosts receive the configured default tags.

Access and scope

Only instance administrators can open and change this page. The settings apply to the current CT-Ops instance.

The page has two cards: Default Data Collection and Default Tags.

Default Data Collection

The Default Data Collection card sets the collection switches CT-Ops uses when a host has not saved its own collection settings. Existing hosts with host-specific settings are not rewritten when these defaults change.

SettingBuilt-in defaultWhat it controls
CPU UsageOnWhether new hosts collect CPU utilisation percentage by default.
Memory UsageOnWhether new hosts collect memory utilisation percentage by default.
Disk UsageOnWhether new hosts collect disk-space utilisation by default.
Local UsersOffWhether new hosts collect local OS users and SSH keys by default.
SaveDisabled until local changes existPersists the default collection settings. The button changes to Saving… while saving and shows Saved after success.

Use the defaults for the normal fleet policy. Use the host Management Data Collection card for exceptions on individual machines.

Default Tags

The Default Tags card stores key-value pairs that CT-Ops applies automatically to every newly approved host.

ControlWhat it does
Existing tag chipShows a default key:value pair.
Chip remove buttonRemoves that pair from the local edit set before save.
KeyDefault tag key. Suggestions reuse existing keys from the instance tag catalogue.
ValueDefault tag value. Suggestions are scoped to the selected key.
AddAdds the trimmed key-value pair to the local edit set. It is disabled until both fields contain text.
SavePersists the default tag set. It is disabled until local changes exist.

Validation requires a non-empty key up to 100 characters and a non-empty value up to 500 characters. Tags are deduplicated by key case-insensitively, with the last value winning.

Default tags are the weakest tag layer. Tags set per-host, on an enrolment token, or on the agent CLI override defaults on matching keys.

Operator guidance

Keep defaults broad and stable, such as env, owner, or platform values that apply to most newly enrolled hosts. Put unusual classification on the host itself so exceptions are visible on the host’s Management page.