nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Why is my Advanced Alert reporting on the wrong Volume?

mkomeara

I've got an Advanced Alert set up to alert via email and to the NPM log when utilization of any of the volumes (C:, E:, or F:) on a certain server (HQDMS1) exceeds 75%. The Reset Action sends an email and posts to the NPM log when the utilization drops under 75%. The problem is that when I test the alert, it reports on a disk drive volume (D:) from a completely unrelated server, but reports it as the CD drive on the HQDMS1 server. The CD drive on HQDMS1 is drive . All the alert and action details are in the attached file.

Orion-Volume-Alert.pdf

Find more posts tagged with

advanced_alert_setup_question

alert_test

Accepted answers

qle

Someone correct me if I'm wrong about this but when you test an alert, it actually tests the trigger action but not the trigger condition.

All comments

mcbridea

Add Volume type = Fixed Disk to the trigger

mkomeara

I added that to the trigger and it made no change to the email alert. The serial number 90780f5e displayed in the email message for Drive is a valid Drive serial number for 354 other Nodes (servers) in our Orion database, but not for this Node. One thing I failed to send earlier is the Test Log, but it appears to be no help either;

7/21/2010 1:28:47 PM: Initiating test for alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Retrieved 2 actions for alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Preparing action type NPMEventLog to test alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Alert WorkSite High Disk Util - Log and Email: successfully wrote to event log. - Volume:D:\ Label: Serial Number 90780f5e Percent Used: 40.05688 Exceeds 75% Threshold
7/21/2010 1:28:47 PM: Action type NPMEventLog for alert WorkSite High Disk Util - Log and Email completed successfully.
7/21/2010 1:28:47 PM: Completed action type NPMEventLog for alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Preparing action type EMail to test alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Email 'Alert Triggered On ${NodeName} - ${VolumeDescription} - ${VolumePercentUsed}' from 'Alert Triggered On ${NodeName} - ${VolumeDescription} - ${VolumePercentUsed}' to '"Alert High Disk Usage HQDMS1" <#DataComm@ExpressPros.com>' has been successfully handed to the local mail handler for alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Action type EMail for alert WorkSite High Disk Util - Log and Email completed successfully.
7/21/2010 1:28:47 PM: Completed action type EMail for alert WorkSite High Disk Util - Log and Email.
7/21/2010 1:28:47 PM: Completed test for alert WorkSite High Disk Util - Log and Email.

qle

Someone correct me if I'm wrong about this but when you test an alert, it actually tests the trigger action but not the trigger condition.

mcbridea

As Ed McMahon would say "You are correct sir!"