

As an example: My projects with cliens start at 20 days for a very basic Solarwinds installation and consulting. Point out to your Management that monitoring a midsize environment is not a task you do when you have other things to do. I am not very familiar with Linux or other UX systems so I would need more thinking and trying on that. The AppInsight templates can be assigned by automatic discovery, however I have seen too many unnecessary IIS-Monitors going red so I would not automatically assign that template. Apply sometihing like this monitor as "default" to your windows machines so you have all that are set to "Automatic" Status / CPU / Memory so you have the Nodes in your system.įor your services: there is a "all automatic Services monitor" for Windows systems: Check All Services Which Set To Automatic Mode Are Running I am not sure if this works with SNMP but you might be able to specify WMI for this. Let a "Network discovery" run with just a few options. It makes life easier for you, at least from my experience with dynamically allocated storage (all other connection options won't work so well when the disk-IDs change) When talking about "core things" in your case I would go and use SNMP on the machines.

> Same strategy -> Import Scripts with API IntegrationĪs a "busy system admin" you can't know everything so someone has to tell you what is important on which machines. Others use a Sharepoint List where I can pull the data to put into solarwinds. But from your last post I see that you would like to rant about the SDK so I assume this might not be an Option for you. My sync-Script has about 1500 Lines of code but does its job on a daily basis for about 4 years now. > Unfortunately this is SDK Programming.

In these cases command is the "leading" System telling Solarwinds what to monitor with which credentials with which baselines. Some of my clients use FNT-Command for this. Do you have some sort of CMDB where your devices/servers/.
