This page covers common questions about using Alert Rules to target or suppress the Low Disk Space alert for specific volumes without affecting other alerts or instances.
Can I apply the Low Disk Space alert rule to specific volumes only?
Yes. When you create an Alert Rule for the Low Disk Space alert, an Objects field set to Disk/Mount Point appears after you define a scope. Use this field to select the specific volumes the rule should apply to. The available drives are based on the instances in your selected scope.
To set this up:
- Go to Admin Console › Alert Rules and click [+Rule]
- Set Alert Type to Low Disk Space
- Set Scope — choose Profiles or Resources (one or many under either option)
- In the Objects field, select Disk/Mount Point from the dropdown
- Search for and select the volumes to include
- Configure the remaining rule behavior (Ignore Alert, Severity, Tolerance, or Notification overrides)
- Click [Save]
Tip: Select All current and future objects to automatically apply the rule to any volume — including newly added drives — within the selected scope.
I have many volumes that follow a naming convention. Do I have to add them one by one?
No. The Objects field supports wildcard patterns alongside individual volume selections — and you can combine both in the same rule.
To add a wildcard, type a pattern into the search field using the percent sign (%) as a wildcard character, then click Add Object.
For example:
| Pattern | Matches |
|---|---|
%Data% |
Any volume with "Data" anywhere in the name |
D:% |
Any volume starting with "D:" |
%Logs |
Any volume ending with "Logs" |
You can add multiple wildcard patterns and specific volume selections to the same rule. The badge on the Disk/Mount Point dropdown reflects the total number of objects currently added.
All wildcard patterns apply across every instance in the selected scope.
How do I decide whether to scope the rule to a Profile or to Resources?
| Recommended Scope | Scenario |
|---|---|
| Profile | You want any new instance added to WISdom to be covered by the rule automatically, without having to update it |
| Resources | The volumes you want to target exist on specific instances only |
| A mix of both | Create separate rules — a wildcard rule scoped to a Profile, and individual volume selections scoped to specific Resources |