Why groups exist
Without groups, every check would either run against every host (noisy) or have to be assigned host-by-host (tedious). Groups give you a stable name and filter for a class of hosts:- “AWS production”
- “Linux production database hosts”
- “Windows file servers”
- “Non-production sandbox”
Create a group
Build the filter
Click Filters → Add and combine the properties you want. For example,
vendor = AWS AND os_family = Linux. You can add as many conditions as you need.Save as group
Once the filter shows the hosts you want, click Save as group. Provide a Name and Description in the modal that appears and click Create group.
How filters work
Filters are evaluated on every agent run, against the most recently captured properties. The group’s membership is dynamic — a host whosevendor changes from AWS to Azure automatically leaves the AWS group on the next run.
You can filter on any property the agent collects. Common starting points:
| Property | Use case |
|---|---|
vendor | Group by cloud (AWS, Azure, GCP) or on-prem |
os_family / os_version | Group by Linux vs Windows, RHEL vs SLES, etc. |
environment (custom) | Split production from non-production |
| Application properties | Group by application role (e.g., web servers vs databases, or — with the SAP integration enabled — by SAP component) |
| Hardware properties | Group by host class for performance baselines |
Edit a group
To change a group’s filter or description:- Go to Hosts → Host groups.
- Click the group, then click Edit.
- Update the filter, name, or description and save.
Delete a group
Deleting a group removes its filter and unassigns its checks. The hosts themselves are unaffected — they remain in any other groups they belong to, and historical check results are preserved.Assigning checks to groups
Groups are the connection point between captured data and compliance enforcement. To attach a check to a group:- Go to Hosts → Host groups → [Group name].
- Click Assign check and pick the check from the list.