mesverrum · Observability Architect · ✭✭✭✭✭

I have my own personal wish list of resources that I pray the devs would build for me so I can appreciate the sentiment. In the mean time, you can build most of the same capabilities with SWQL queries if you learn how to do them or snag them from the Thwack community. I don't have time to rework the queries for Interfaces…

LEM doesn't natively attempt to do anything like that, it just takes the data in the log file as it received it, processes it as is and saves it. Doesn't allow you to modify the data or add info from other sources. I don't think any of those kind of features are on the road map at all right now.

First of all, to fix them showing up with the wireless device view you will need to go to your Orion settings > Views by Device Type, find their machinetype in that list and change them from Wireless to Default. This is a common behavior in NPM that I hope will one day stop. As far at the network atlas topology you are…

Nothing built in, I've seen some tricks to do it using combinations of custom html or java script, but nothing native to solarwinds.

SELECT n.caption, s.name, s.version, s.installdate from Orion.AssetInventory.Software s join orion.nodes n on n.nodeid=s.nodeid where s.name like '%.net%' and n.vendor = 'Windows'

Discoveries always only add to things, for example if you uncheck an interface that you were already monitoring then it would not get rid of it, since the discovery can only add new pollers and objects

ESXI hosts have a thing called Host Profiles that should be able to handle this kind of stuff, but I could believe that if the hosts are in many locations but all locations use the same template they wouldn't put that into the profile.

From that node's details page, or from manage nodes there is a button called list resources that will browse the node to figure out what is available to monitor, then you just check the boxes for the disks and interfaces you want to monitor

I've only ever used the automatic addition with scheduled discoveries, so that may be the case, will have to play with it to experiment

Typically there is a pretty standard list of problems that cause this. First of all, verify that the SNMP/WMI credential you are using on the node still works from the edit node page. If this gets changed then your node will still show as up because we can ping but wont get any of the detailed stats and that unknowns begin…

Yeah that's what I would expect to do as well, there is already a component available for pop3 service monitoring, it just isn't part of the appinisght template.

Yeah, I say the same things to my clients all the time but the work still gets done and they are happy to have us back for more

It holds traps, syslogs, and if you have VMAN it will also collect vmware events. They all get dumped into the same database tables and just get sequenced as they come in and tagged by where they came from. If you made those rules to just discard all events then I expect it should have stopped growing.

Building out your dependencies would fix that issue with 150 nodes emailing you at once, you would get notified that your edge router or whatever is down and everything you have indicated as being downstream of there gets marked unreachable and doesn't trigger emails. Define and use dependencies in Orion NPM - SolarWinds…

There are browser plugins you could install that can refresh any page you want at any interval, this would likely be your best option. It is also worth pointing out that most of the polling in solarwinds happens in increments of minutes so refreshing the pages that aggressively seems like it would not have any new data on…

This is a stripped down example of the type of logic I've used. In this example the alert would have the same name but with a priority on the end, so I have a cpu alert p1 and a cpu alert p2, you can go on to include additional priorities if you want to type them all out. The p1 alert is just set up to alert when critical…

It's just a problem with your use of and/or By OR'ing multiple <> nodeid then you effectively make it so all devices match the condition all nodes would match the logic of (not node A OR not node B) you need AND's when you are trying to use negative matches Community='{Community-String}' AND interfaces.NodeID <> 11111 AND…

I would think that the easiest way to build something like this might be to make a copy of the UDT summary page and then apply a view limitation to it to to narrow it down to the nodes you want.

The discovery does not create new nodes or change your custom properties, it would just automatically change the polling method if it finds a successful cred. I use this technique all the time with clients who have a large number of unknown devices.

yeah, NCM was a completely stand alone product years ago, so it already used a GUID based node id scheme. The cirrus.nodes view will have both the cirrus nodeid and the corenodeid so you can correlate them.

I'm on mobile right now so I can't grab the link for you, but Google solarwinds sdk github and download the sdk to your server and you will be able to browse the swql layout

It's really up to you when you think you are better off rebuilding, it is a fairly complex process for most environments of any size, new server, new database, and need to set up all you nodes and custom properties and alerts and everything again. It's likely to be less effort to just upgrade what you have, but if its…

There should be no need to mess with licenses or perform discoveries to see your old nodes. If the migration went correctly then you would have exactly the same data in your new instance as was in the old one. Look at the restored backup of your old system in SQL and see if the nodes tables have the missing devices from…

So this turned out to be pretty tricky to get it working and looking how I wanted it to, but this is what I came up with So this is a 24 hour chart with the numbers broken down per hour, set it to display using columns because lines/area get ugly gaps for any periods where you didn't have any alerts. I didn't have many…

Without a doubt the database is by FAR the most common bottleneck that I see in client sites. Using the wrong raid types is super common and is an absolute killer for the database. Another one that your DBA likely already saw is that many people forget to set up any kind of SQL maintenance, such as defragging the indexes.…

If it is supposed to ensure that this process is running all the time then the easiest thing to do is just skip the batch file completely and just tell solarwinds to check for that process/service Real-Time Process Explorer

1 main difference is that you need to deal with agents (I find them to be a nuisance to stay on top of when they stop working for various reasons). They also give you the option to do the application dependency mapping that you can't do without them. 2 if your firewall is stateful it should allow the ephemeral ports to…

Another flavor of this report that works better for large sets of servers is this one select n.caption as [Server Name] ,'/Orion/images/StatusIcons/Small-' + n.StatusIcon AS [_IconFor_Server Name] , n.detailsurl as [_linkfor_Server Name] ,case when n.cpuload < 0 then 'Not Polled' when n.host.nodeid is not null and…

I will just throw this out there, I have posted the foundations of such a report using SWQL and/or SQL in several threads but I think that uptake has been marginal so I haven't spent further time on it. This morning I fleshed it out a bit further but I have been very busy and haven't been able to allocate more than 20-30…

You can do all the date calculation stuff in PoSH if you like but its easy to do directly in the sql by adding a where condition such as "where minutediff(keepalive,getutcdate())>10 --only shows engines that haven't updated in the last 10 minutes"