mesverrum · Observability Architect · ✭✭✭✭✭

Comments

  • Select TOP 30 nodes.NodCaption, nodes.AgentIP, audit.DateTime, audit.Message FROM NCM_RTNAudit audit JOIN NCM_Nodes nodes on nodes.nodeid=audit.nodeid ORDER BY CONVERT (DateTime, DateTime) DESC
  • No. You could use excel to build a list of all those .1 addresses and then copy those into the ip/hostname discovery.
  • Are you working on requirement 6.5.10? LEM is mostly just basic Linux under the hood so perhaps this guide would be of some assistance? Don't know offhand if they do anything unusual that would interfere with this but this explains how to set timeouts in Linux. How to set an SSH timeout | GoDaddy Help Support can get you…
  • Building automation and deep reporting from SAM has always been a bit of a struggle. Would be nice if there was at least some tables with indexes of what things were supposed to mean (for example, theres not list translating componenttypes to a friendly name). I know those tables well from smashing my head against the wall…
  • SQL does not allow you to use an alias inside the Where conditions, use Nodes.Caption instead of nodename
  • Each node is tied to one single poller, all tasks for that node will come from the same poller. At a minimum you need access for the one poller you use to monitor the node, but I find it is a best practice to add all possible pollers (except things like pollers on another network that couldn't reach the node to begin with)…
  • Swisentity is basically "whatever triggered this alert" so depending on the type of alert you are making it could be a node, interface, component, whatever you selected at the top of the trigger tab. If you have an alert triggering on an interface for example then the Machinetype field doesn't exist for interfaces so it…
  • They don't do a great job of displaying this stuff in the default resource, but the way I handle this is to add in a UNDP monitor for each of the columns of the table that im interested in. Ideally set them all to the same column for the label. Then just hit edit on that UNDP table resource you screenshotted there and…
  • The official solution to this problem is just to build scheduled discoveries of your server subnets and have it automatically adding in all volumes that it finds. This also helps a bit with the problem of making changes to a volume in vcenter and having it get assigned a new serial number and the old volume shows as down…
  • Depends on what features and modules you intend to use. Any device with standard SNMP support is "compatible" with solarwinds in a general sense. The most common issue for less common devices is that the out of the box hardware health monitoring might not be set up to poll the OID's used by your device, this is the current…
  • You can set up a discovery, check the box on the second screen where it asks if it should update agents. The only limitation right now is you'd have to add all fixed disks, discovery doesn't allow you to do things like "only add c or d drivers but ignore any others"
  • Fastest way in the GUI is a report with a custom chart, or a custom table if you prefer to export the raw data out to another tool. Something where you set the data source to be components where the name = "Your agent" and then add in the columns for cpu load to the chart. Initially it would give you a separate row for…
  • Wouldn't you be able to declare the services array, and then add in arg(0), arg(1), and arg(2) ? would probably have to build in some error checking to validate how many args are actually being used and such.
  • No need to monitor each host, point at vcenter with API credentials and it will populate the necessary info for the hosts under the vcenter, including hardware sensors and such. If you do set up SNMP on the hosts directly it adds the ability to monitor the local storage and specific NICS.
  • I usually build myself a home view called SW Admin and have a collection of reports I've built up over the years that track these kinds of things for me. I'll upload some of them tomorrow but the first thing on the page is a chart showing the polling loads on each server so I can watch for balancing issues, I've never…
  • For the most part the storage metrics being collected are wrapped around iops/throughput/latency. Out of the box, assuming you have all the relevant licenses, Orion would be monitoring the write latency (shows as disk sec per transfer)and queue depth of all volumes at the monitored OS level for any system using WMI or the…
  • Something like that would require a script based monitor I suspect. You'd need to write a script to parse out the necessary info and just output that as a statistic. If the log file is coming from Windows servers then you'd need to do it in powershell, Linux probably perl. Are you familiar with either?
  • You would probably want to set up a User Defined Group that contains those ip's, then just edit your rules to only trigger on events where the source machine is not in that list. These links should help you with some of that Get started with user-defined groups Create Rules in Your SolarWinds Log & Event Manager Console -…
  • There nothing in the software to facilitate that at this time, would need to create it as a feature request. In the interim you could report from the secondary using something like SSRS.
  • This is the custom query I use for that scenario, shows devices that are pinging as up but snmp/wmi/agent have stopped working for at least 20 minutes. select n.caption as [Node] ,n.detailsurl as [_linkfor_Node] ,'/Orion/images/StatusIcons/Small-' + n.StatusIcon AS [_IconFor_Node] ,n.ip_address as [IP Address]…
  • The Web reporting tool does not, to the best of my knowledge, allow you to create custom data columns that aren't already in the database without creating the source from custom sql/swql. If there is already a field in the db you can select it, if you need to modify the data in some way then you have to change the…
  • SAM has server warranty end dates for a few brands of servers, but nothing I'm aware of tracks actual hardware life cycles. Wouldn't be too hard to cook something up using custom properties if you had a data source with the hardware life cycle info.
  • None of those, the topology mapping is not instant, and often takes a significant amount of "post processing" that has to be done by hand, no api or programmatic capability exists. There is no capability to live data beyond re-running the discovery that created the map initially.
  • You can make it so a user only has access to groups using their account restrictions, but they will lose access and visibility into any other nodes. You do not have the option to, for example, say a user can see all nodes but only admin some of them. See this part of the admin guide Restrict user access to network areas by…
  • It can be done, but it isn't easy unless you are pretty familiar with SQL and VERY familiar with solarwinds. You'd be working with the views, resources, and resourceproperties tables Pretty straightforward, views lets you know which view you are working with (probably what you will be filtering on) then join the resources…
  • You probably wouldn't use the Groups feature in orion to do this, but yes you can modify the polling interval from the manage nodes screen and use whatever criteria you can come up with to group them all up and just check all their boxes before you hit the edit properties button.
  • you would just need 2 separate alerts, the action repeat intervals don't have any conditional logic you can apply to them.
  • NTM has no API or similar capabilities.
  • Interface is a child object on a node, specifically it is a network port. Sometimes they are physical interfaces and others are logical/virtual Switch A = Node Switch A Eth0/1 = Interface Switch A VLAN100 = Interface -Marc Netterfield Loop1 Systems: SolarWinds Training and Professional Services * LinkedIN: Loop1 Systems *…
  • Unfortunately the windows cpu poller is a point in time measurement, as opposed the the way you would see the 5 min running avg in linux. You can check more often and set your alert trigger condition to require longer waits but unfortunately the metric is going to be what it is. A couple years ago I tried to script up a…