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

Alerts not working for servers monitored via the Agent, but the alert works for server using SNMP.

clausendb

Just a started using the Solarwinds Agent on a few of my Windows servers. I have been using SNMP for ever. I have an alarm configured to alert when any disk drive being monitored goes below 1GB free. This has been working for years.

After getting the agent setup on those two Windows servers, I purposely filled up the C: drive on one of them to get it below 1GB free. I did the same thing to one of my servers that alerts correctly on disk space below 1GB.

The SNMP server sent the alert no issues. The Agent server did not send anything. I checked the Agent server's disks in Orion and it did show the disk in question as 100% full (550MB free in reality).

Any ideas? I have searched the Interwebs and asked Uncle ChatGPT - NADA.

Find more posts tagged with

Alert

orion

npm

Accepted answers

clausendb

I found the answer; The Department field was blank. Once I added a valid department to the Department field, alarms started to shows and alerts were sent.

You're welcome LOL.

All comments

vinay.by

@clausendb - Which version of SolarWinds are you running on?

Check your trigger conditions on the existing alert - if its applied to all objects. If it is then ignore this statement.
Can you test one more thing - Can you create a new alert with same conditions and check if that works as expected for both agent based and snmp? Dont duplicate the existing alert, create a new alert from scratch.

Please let me know if this works.

clausendb

Orion 2026.1.1

Original Alarm :

Created a new alarm as suggested:

No change with newly created alarm.

One thing I forgot to mention; While these drives I fill up as a test do shows as full under the device in question, they do NOT shows under active alarms which might be the reason for no alerts being sent.

vinay.by

Only following set of objects : Show lists (do you see your drives here ?) Set it only to the device in question or disk in question.

And maybe change trigger condition, try using % available rather than bytes - only for testing. Maybe this is why its acting different for SNMP based vs Agent.

vinay.by

it definetly is strange, data is there and SolarWinds alerts wont act on it.

The new alert that you created can you restrict it to only the devices and volumes which has an issue, maybe that can explain more.

clausendb

I tried making it only monitor the single device - issue did not change.

I've been trying to make this work for 5 days now and the only common denominator is Agent vs. SNMP Agent does not work.

clausendb

I found the answer; The Department field was blank. Once I added a valid department to the Department field, alarms started to shows and alerts were sent.

You're welcome LOL.