CT-Ops

Global Check Settings

Global CT-Ops settings for reusable host check templates and default check-alert rules.

The Global Checks settings page creates reusable check templates that can be assigned to hosts. Open it from Settings -> Monitoring -> Global checks at /settings/monitoring.

Templates are not evaluated by themselves. CT-Ops evaluates a global check only after it has been applied to one or more hosts.

Access and scope

Only instance administrators can create, delete, or apply global check templates. The settings apply to the current CT-Ops instance.

Host operators use these templates from the Assign global checks control on Host Monitoring. Alert instances created by assigned check-alert rules appear on Checks & Alerts.

Check templates table

The Check Templates table lists reusable checks.

Column	Meaning
Name	Template name copied to the host check when applied.
Type	Check type, such as port, process, HTTP, certificate, disk space, file size, Docker volume size, patch status, service account, or SSH key scan.
Target	Compact summary of the check configuration, such as host and port, URL and expected status, path and threshold, or patch-age limits.
Alert	Shows Off when the template has no failure alerts, or one badge per configured alert rule with severity and consecutive-failure threshold.
Delete	Removes the template. Existing host checks already assigned from the template are not removed by deleting the template.

If no templates exist, the page shows an empty state and prompts an administrator to add one.

Add global check

Select Add Global Check to create a template.

Field or control	Default	Validation	What it does
Name	Empty	Required, 1 to 100 characters	Name copied to assigned host checks.
Check type	`Port`	Supported check type	Chooses the form fields and check behaviour.
Interval seconds	`60`	Integer from `10` to `3600` seconds	How often assigned host checks should run.
Add Global Check	Disabled until Name contains text	Requires administrator access and valid type-specific fields	Saves the template.
Cancel	n/a	n/a	Closes the dialog without saving.

Type-specific fields:

Check type	Fields and defaults	Validation and behaviour
Port	Host defaults to `localhost`; Port defaults to `443`.	Port is limited to `1` through `65535`. Checks whether the target TCP port is reachable from the host.
Process	Process name defaults to empty.	Process name is required by the check configuration. Checks whether a matching process is running.
HTTP	URL defaults to `https://example.com`; Status defaults to `200`.	Status is limited to `100` through `599`. Checks the URL and expected response status.
Certificate	Host defaults to `example.com`; Port defaults to `443`.	Port is limited to `1` through `65535`. Checks remote certificate state for the endpoint.
Certificate file	Certificate file defaults to `/etc/ssl/certs/cert.pem`.	File path is copied to assigned host checks.
Disk space	Path defaults to `/var`; Mode defaults to `Used`; Threshold defaults to `80`; Unit defaults to `Percent`.	Threshold must be numeric. Use Used to alert when consumption is high; use Free to alert when remaining space is low.
File size	File path defaults to `/var/log/app.log`; Operator defaults to `Above`; Threshold GB defaults to `1`.	Threshold must be numeric. Checks whether file size is above or below the threshold.
Docker volume size	Volume name defaults to empty; Operator defaults to `Above`; Threshold GB defaults to `1`.	Threshold must be numeric. Checks whether a Docker volume is above or below the threshold.
Patch status	Max age days defaults to `30`; Max packages defaults to `500`.	Max age is `1` through `3650` days. Max packages is `1` through `1000`.
Service account, SSH key scan, Log scan	No extra fields in this dialog.	Uses the default configuration for the selected check type.

Alerts on failure

The add dialog includes an Alerts on failure editor. A template can stage up to 10 failure-alert rules that are copied to each host when the template is applied.

Field or control	Default	Validation	What it does
Add Alert	n/a	Maximum 10 staged alerts	Opens the alert editor.
Severity	Warning	Info, Warning, or Critical	Severity assigned to the alert rule created for each host check.
Consecutive failures	`3`	Integer from `1` to `10`	Number of consecutive failed check results required before CT-Ops creates a firing alert instance.
Save	n/a	Requires valid severity and threshold	Adds or updates the staged alert rule.
Remove	n/a	n/a	Removes a staged alert before saving the template.

Use multiple staged alerts when the same check needs different escalation thresholds, such as a warning after 2 failures and a critical alert after 5.

Apply to hosts

Select Apply to Hosts to apply every global check template to every host in the instance. The success message reports how many hosts were updated, how many checks were created, and how many alert rules were created.

Applying global checks replaces only checks that were previously assigned from global templates. Manually created host checks are left in place.

On a single host, use Assign global checks on the host Monitoring Checks tab. It applies the current global templates to that host and reports the number of checks and alert rules assigned.

Operator guidance

Use global checks for fleet-wide expectations such as SSH reachability, web health endpoints, patch-age policy, required services, or important disk thresholds. Keep templates generic enough to apply broadly, then add host-specific checks for unusual machines.

Review templates before selecting Apply to Hosts. The action can create a large number of host checks and alert rules in one operation on a large fleet.