jokerfest · Systems Engineer · ✭✭✭✭✭

yeah, i read other articles too and it didn't help

Yea, I just noticed it in today's email also.

I made a custom property to tier the alerts as needed. Alert levels high-low 1-3. It was hard placing all nodes from the start, but worth it now. It's easy to demote a device to a lower level if you know it will not be reaching the performance metrics for level 1 regularly and it's a non-factor.

we call it read-only Friday

I like it.

Yeah, I think I've had problems in the past uploading from a network share or a mapped drive. Make sure the file is local to the machine you are uploading from.

Maximum memory setting on SQL Server is incorrect - I have it right where I want it Automatic Root Certificates Updates Check - How does it run a check if the check always fails whether you have it fixed or not? (This one annoys me the most somehow.) Identify pending Windows reboot - No, there is never a pending reboot.

My Information service v3 touches 40-50GB and completely hangs the server.

Ugh. Nothing is worse than finding what looks like the perfect link to solve your problem, only to get the 404 black hole page.

I guess there would be another step that might either seem implied or not necessary: 2.5. Assign the new transform poller to all the nodes that already have the first poller. I hope that's your issue!

It should be a pretty fix for you. 1. Open the Universal Device Poller on your main Orion server. 2. Go through the Transform Results Wizard to make a new value. 3. Use the new field created to graph and alert off of. (So use WatchDogTempConverted instead of WatchDogTemp.)

You may have hardware limitations and/or hard-coded ip addresses keeping it the way you do, but yes, move as many elements as you can to the additional poller. Please look into a additional web server if you have the hardware resources. They are very inexpensive and could help you a lot. Good luck!

be careful what you wish for, you just might get it PS: I'm not a hater, I'm currently expanding our environment. I'm surrounded by SolarWinds swag and would defend it to the death to anybody on the street. But here is a 'safe' place where I can say I have been left with a sour taste in my mouth over the last couple years…

Yeah that sounds crazy. Do you have an absolute ton of web users? "SolarWinds Information service V3 is used by websites to talk to the database. This service also controls how polling engines communicate with each other."

Wow that sounds like you should be just fine. Are you using default polling times? Were you having the save issue before 2025.1.1? I'm still on 2024.4.1 waiting for the next version to be released. My main server v3 process is only using ~1.5 GB of memory, but it only has a couple hundred elements. I'm spread across…

That was my first thought as well, but I went the other direction. I'm glad you brought it up.

More important than Nodes, how many Elements are you monitoring? Go to Settings - All Settings - Database Details Then scroll down for Total Elements Depending on the version of SolarWinds you are running the recommended number could be 10k, 40k, or 100k.…

This is good to know. My texts seem to get throttled when we have a major event that sends hundreds of texts. They stop for a while, then are released in smaller batches hours later.

If I understand correctly you have two separate alerts, one for down and one for up. Is there a reason for doing that instead of creating one down alert and then using the reset action of that as the "up alert"?

You just described (what I have found to be) the textbook definition of their current technical support workflow. Source: 12 years of using the product.

oh wow, best of luck!

I don't have one personally, but I would assume it would be discovered by SolarWinds just fine with SNMP. Any Cisco hardware is usually trouble-free.

my disk alerts don't show in that widget, I'm assuming it's because they are volume based alerts and not node based alerts?

oh - so your alert is working fine, it's just not showing in the widget?

Let's see a screenshot of your trigger conditions

Sounds good. Glad you got it going.

I actually have an online installer from two days ago and it gives me that exact same error. I held off on the upgrade when I heard about the new release.