Comments
-
Orion does not have that out of the box, if we are not talking IIS-servers and using "Appinsight for IIS". Then you have that info. Otherwise you will need to create a powershell script running against all servers to collect that info first. Then you can create a report.
-
You might look to see if you can get some of that info out from SNMP. That you can use with NPM and UnDP's
-
No you need SAM for that
-
Hmmm, traps=180 days. A bit long. Don't think it has changed recently.
-
What you see in the GUI is one thing and what is alerted on is another thing. If you want an alert if a node is warning, critical or even ok, you can do that. But all alert rules you want to have you have to enable or create. There is a whole bunch of alert rules created out of the box but you can also create your own.
-
Yes they are.
-
All SAM script want an Integer as output. That's what Orion alerts on. But you can also have a text field so clarify what is happening. The output should be like this: echo "Statistic: [Your number]" echo "Message: "[a text message if you want]" So you are probably adding the wrong info to the message output. See here for…
-
I see that also in one installation. Have several customer installation that I manage but only one have this. The Log Analyzer for Orion Polling Service is eating VirtMem. Not a high load on traps or syslogs. Got 2020.2.6 HF1.
-
Hi, if I understand your script correct the output is some text fields. It has to be an integer, a number. https://documentation.solarwinds.com/en/success_center/sam/content/sam-linux-unix-script-monitor-sw3260.htm All SAM script want an Integer as output. That's what Orion alerts on. But you can also have a text field so…
-
Logs are good to check but the installer will tell you if something went wrong, of what you can see in the logs anyway. I would wait about 20 to 30 min or so. Then check some nodes, applications and so. See that I get new data. Check polling engine and see all deliver data. Check "My Orion Deployment page" to see all…
-
You can't copy it directly but has to recreate it. If you have alot of custom swql you can use them in modern also. Might need some tweaking to get them correct there. A good start is to look at these blog…
-
I think there is one AlertObject per node and triggered alert. So if a node has triggered three different alerts in it's history there will be three rows in AlertObjects
-
Yes I do. In Script argument i have "IP to test against (dbserver), port to test against"
-
Does the script work if you run it manually on the application server? I use below as a general way of Orion asking another server to check connectivity to a third server. Not a fancy SQL login as you do but it will show if it can connect anyway. $Client = '${IP}' $ClientPort = "5985" $Server = $args[0] $ServerPort =…
-
"Normal" Polling engines can be stacked. Meaning you can add several Polling Engine licenses to the same windows server thus being able to poll more elements from that windows server.
-
If you have SAM with component based licensing you DON'T have free polling engines. You only get free Polling engines if you have SAM with Server based licensing. The free SAM Polling Engine is for SAM based monitoring only.
-
I got this at a customer last week also. They added a new SAM25 license, they thought, but got a SAM1. A call to support and license department and they changed the license code in customer portal. Changed license code in Orion and they got the correct number again.
-
Don't use AppOptics so can't say there. PerfStack - always demonstrate it in my sales meetings with new customers. The ease of displaying and correlate data is fantastic. Save perfstacks for later is helpful. Shows the benefit of having one platform, Orion, to monitor the whole it infrastructure.
-
Normal node polling is NOT done with WinRM but with WMI over DCOM/RPC. Only SAM polling is using WMI over WinRM at the moment.
-
If you add a node as "External Node" Orion will not ping it or anything, it's just a "place holder" for situations like this. Add that and assign your URL-monitoring to that external node.
-
I think it will be kerberos or ntlm depending on what the Windows settings are. Hope so anyway...
-
Message queues like MSMQ can be monitores. Many others as well. By "component services", do you mean normal services then? If so yes they can be monitored both regarding status and resource usage. SAM is the module for that.
-
Hi, I would start by enabling debugging and see if that gives any more clues. Next would be to check out the event log on the monitored server to see if they gives any info. https://support.solarwinds.com/SuccessCenter/s/article/Turn-on-application-debugging-for-SAM?language=en_US
-
See https://thwack.solarwinds.com/product-forums/server-application-monitor-sam/f/forum/92517/widget-to-display-volume-capacity-changes
-
Strange, I would take a look in the database with SWQL or SQL to see how the values look for the "Null-instances". Does it have any value? Are only the last poll missing values? Hope that can give you an idea.
-
Hi What do you think about this? SELECT N.Caption AS [Node] ,V.Caption AS [Volume] ,Round(MIN(DiskSize)/1024/1024/1024,0) AS [MinDisk_GB] ,Round(MAX(DiskSize)/1024/1024/1024,0) AS [MaxDisk_GB] ,N.DetailsUrl AS [_LinkFor_Node] ,V.DetailsUrl AS [_LinkFor_Volume] --,PercentDiskUsed FROM Orion.VolumeUsageHistory AS VS INNER…
-
If you do a "list resources" on that node, do you see any volumes then? If so you need to check the once you want to monitor. If "List resources" don't shoe any volumes there might be an issue with snmp on that node. Don't know linux snmp enough to assist there.
-
Polling every 24 hours, then you will never know for sure when during the day it polls. Option 2 will probably be the easiest. The other option is to add a check for the time in the script, so the actual file check only runs during the hours you want.
-
If you monitor the server and have checked "asset inventory" you should on the servers node page have a tab to the left called "Asset Inventory". There is a widget with all installed software. You can also create a report based on this information.
-
Where do you want to disable NTLM? On the whole Orion windows server? I guess Orion then can't talk to nodes that use NTLM but that might not be an issue on your case. I think it will be fine if you do so.