The High Storage Utilization alert can be scoped to more than one device category. If the alert is limited to the Network Device tag, servers are outside its scope and will not trigger it.
Before changing the alert, confirm how the servers are monitored in Auvik. Network devices, VMware hypervisors, and Windows servers may expose different storage entities and metrics. The correct alert type and entity scope depend on that representation.
Why servers may be missing
The preconfigured High Storage Utilization alert uses the Device Storage Utilization trigger and, by default, applies to the Network Device tag. Adding servers to the entity scope is appropriate only when those servers expose the same device-level storage metric.
Windows servers monitored with Auvik Server Monitoring expose storage as disk partitions and use the Disk Partition Utilization trigger. Server Monitoring requires the endpoint agent and an Auvik collector that can discover and reach the server.
Add servers to the alert scope
1. Confirm server representation and data collection
For each server category, confirm that:
- The device appears in Auvik inventory with the expected class, such as Server or Hypervisor.
- The required monitoring method is enabled. For Windows Server Monitoring, verify that Server Monitoring is enabled, the endpoint agent is installed, and the collector can reach the server.
- The relevant storage value is populated. For agent-monitored Windows servers, verify disk partition usage rather than assuming that the network-device storage metric applies.
2. Review the existing alert
- Go to Manage Alerts > Alerts or Alerts v2, depending on the alert definition.
- Open High Storage Utilization and choose Edit.
- Review the current device selection under Entities or Device Selection.
- Note whether the alert is applied to Devices with this tag, Devices that match these conditions, or a manually selected device list.
3. Expand the entity scope when the metric is compatible
If the servers expose the same device-level storage metric, add the applicable server scope:
- Add the Server and/or Hypervisor device type.
- Add a server tag, such as Server, Hypervisor, or a custom tag used by your organization.
- Add individual servers explicitly when only a small set should be monitored.
When using multiple like device-type filters, Auvik treats them as an OR group. Review the matched-entity count before saving to confirm that the intended servers are included.
If a server is not returned by the selection, correct its Auvik classification or add the tag rule that identifies it. A tag used by Alerts v2 represents the devices defined by that tag when the alert executes.
4. Use the server-specific alert for Windows disk partitions
For Windows servers monitored with the Auvik Endpoint Agent, create or edit a server-specific alert instead of relying on the network-device alert:
- Go to Manage Alerts > Alerts v2 and select Add Alert or edit the relevant alert.
- Set Apply Conditions to Disk partitions on a device.
- Select servers using an existing tag, a new tag, matching conditions, or explicit devices. A useful condition is Device Software Version contains Windows Server.
- Set the trigger using Disk Partition Used (%) or Disk Partition Used (GB).
- Add Disk Partition Name when the alert should apply only to a specific partition.
- Configure the trigger message, delay, and notification channels.
- Define a clear condition below the trigger threshold, with a buffer to prevent repeated alert/clear cycles.
- Save the alert.
This approach also makes it possible to use different thresholds for server partitions than for network devices.
Tune thresholds by device category
Servers and network devices often have different storage behavior and operational requirements. Consider separate alert definitions when they need different:
- Trigger or clear thresholds
- Alert delays
- Severities
- Notification recipients
- Partition-specific rules
For example, a server’s system partition may require earlier warning than a network appliance, while a backup or data partition may need a different threshold altogether.
Validate the change
After saving:
- Confirm the alert’s matched-entity count includes the intended servers.
- Verify that the selected servers have current storage or disk-partition data.
- Test with a temporary threshold on a non-production server or test partition.
- Confirm that the notification is delivered and that the alert clears when usage returns below the clear threshold.
- Restore the production thresholds after testing.
If a server still does not alert
Check the following:
- The alert is applied to the correct site or organization hierarchy.
- The server is included by the tag or device conditions.
- The server has the required agent or monitoring service installed.
- The collector can reach the server.
- The alert uses the metric exposed by that server’s monitoring method.
- The alert delay has elapsed and the trigger condition is still true.
- Another alert definition, suppression, or notification configuration is not preventing delivery.
Document the device types, tags, sites, metrics, thresholds, and exceptions covered by each alert. This makes future classification or tag changes less likely to remove servers from storage monitoring unintentionally.