Comments
-
Hi t0ta11ed74 Did you find what was causing this error and we you able to fix it? I am getting the exact same error for Windows PowerShell Monitor. Only difference is that it's not random. The monitor is consistently failing with this error. I am poling frequency set to 300 seconds. Did you change polling frequency? And if…
-
Hi ttl, I am trying to find the same. Were you able to find a way to check whether and email alert was sent or not for a monitor?
-
Finally it worked for me: Write-Host ("Statistic:{0}" -f $resultsDataTable.Column1) is what I needed and now is working. Thank you again :-)
-
I found how to turn on the debug log here: Turn on application debugging for SAM - SolarWinds Worldwide, LLC. Help and Support The monitor is still failing for me (showing NaN) and when I changed the statistic line to "Write-Host ("Statistic: " + $resultsDataTable.Rows.Count)" it shows 0. So I think there is something…
-
Thank you for your reply frak. I ended up using a SQL Server User Experience monitor using a customized SQL provided by DBA.
-
I think I found the problem. I had created 1 monitor and it was working fine for 10 pairs of output. So I went ahead and created a copy of it and modified it for the minor changes in SQL query and other changes. This second monitor was giving me error. When I deleted the second monitor and created it manually instead of…
-
Hi, Did you find out a resolution for this error? I am also using "Windows powerShell Monitor" and getting this error for a monitor that shows 10 output pairs.To make it even weird for me, I have another monitor in the same template where everything else is same except a minor change in SQL that selects 10 rows from SQL…
-
This is not exact solution for your question but just wanted to share it! We are monitoring Always On instances using custom SQLs provided by our DBA :-(
-
dmacphail Did you find a solution to this? If yes then can you please share as I am also trying to do the same with list of select nodes.
-
Hi. I am interested to know if this feature was made available. I have a case where I might be able to use this feature but I can confirm that only after having a look at it.
-
I had to update this line to include DRIVER={SQL Server}: $conn.ConnectionString = "DRIVER={SQL Server};Server=IP_ADDRESS;Initial Catalog=DB_NAME;Uid=$username;Pwd=$password;" It solved mt problem.
-
Finally, this worked for me: ${Application.Custom.<custom_property_name>} Just so that if someone comes to this thread for same issue.