twomonkeysayoyo ✭✭✭✭✭

This is documented as being a feature, here : https://documentation.solarwinds.com/en/success_center/la/content/la/la-syslog-trap-parity.htm but I can't figure out how to do it. How can we really be expected to 'upgrade' to this product with traps?

It's a horrible implementation detail for us having to api poll a service, that service providing an array of names that have other information and having to dynamically define these. One thing I think my monitor should do is tell me what I don't know. This particular issue causes me to have to know something before I can…

I would engage support. We stopped updating our agents from the console. If I remember correctly the system will queue about 20 or 25 systems and never remove a stuck one from the queue. So when you have many many agents as each 'stuck' one will occupy a slot in the queue effectively shortening the queue of working…

We had same issue. Support was clueless to this enabling of a long-standing feature.

01559630 & 00814594

Our process could not be going more poorly. We have decided we must skip to 2024.1 from 2023.2.0 but it's not going better. We've been attempting, rolling back, and upgrading over the last 3 months with Solarwinds Premier Support and we still haven't (after 6 attempts) managed a successful upgrade with functional,…

That means creating an alert and trigger action per alert per severity. That seems silly.

I'm also struggling with this exact thing. Seems like the "select substring" may be causing the issue?

With a mass deployment method is there a way to pre-select the resources to be monitored? It seems like a nightmare to have to go into 50 servers and check each filesystem.

This worked for me but support may have a better workaround regarding changing a line in a .NET config file. Before installation: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config Change the line <runtime /> To: <runtime> <generatePublisherEvidence enabled="false"/> </runtime>

thank you.

but is it required? WMI is not an option at this point in this environment. CAN it be done with Agent?

I have these failover clusters in my environment. I.E. {Member1, Member2, VIP} I am monitoring Member1 and Member2 with Agents (not WMI or SNMP). By what method should I be monitoring the VIP?

Thanks! In my case I had no reason to suspect this was being redirected but turning off 'follow' worked like a champ.

Just a follow up to my earlier comment...the following is what I implemented to incorporate the custom property with the volume forecast: LEFT JOIN Orion.Nodes nodes on nodes.NodeID = VolumesForecastCapacity.NodeID LEFT JOIN Orion.Settings s ON s.SettingID = 'ForecastMinDays' WHERE VolumesForecastCapacity.DaysToCriticalAvg…

This is really interesting, I came here looking for a forecast SWQL that would allow me to filter on a custom property of the node the volume is attached to (specifically only our production nodes). I'm having a lot of trouble figuring that out. Will post a separate post on it, though.

I know this has been answered above by a really complicated 'get intimate with your database' answer but why wouldn't you just have the event (I.E. Last boot time changed) send a trap to your poller and alert on that threshold?

For those coming after me I ended up just setting the trigger action on this to send a trap to my poller and using the trap filter to set up a threshold per node that sends an email to a ticketing system.

duration isn't an option with this trigger, unfortunately (see screenshot).

I started using the MS IPAM (2012) until I could get something that really manages and tracks IP's. It's been a disappointment. The interface is pretty horrible, and determining what you have is a real issue. You are still connected to the MMC for tracking down a MAC, making CHANGES is very difficult. Adding new IP's is ok…

Ok, figured it out. Was dumb. For some reason I don't understand the line needed to be: AND nodes.CustomProperties.n_production = TRUE