martian_monster · Lead System Engineer · ✭✭✭✭✭

Error out of Alerting Service Log but not sure what it means. I have this feeling I missed something that MS may have changed. As a test I setup a new webhook to a different Team and it still did not fire off.

MPE gets rebooted Nightly and I rebooted APE this morning. Single Node SQL Cluster I checked logs on both nodes and nothing there. I have yet to check out RabbitMQ and see if that is the issue. This started on 7/5 - and we were in a change freeze due to holiday so no one changed anything. The only thing I can think of is…

Yeah completely posted in error. I was trying to delete it but could not figure out how to delete.

Looks like Solarwinds To ServiceNow is not generating tickets now...

I will give that a try. This was what ours was set as "application/x-www-form-urlencoded". This is kind of an odd issue to just stop happening on a random day lol

YAAY! There is an error 2023-07-10 01:36:54,896 [8] ERROR AlertingLogger - (null) Failed to execute an HTTP request. Method: POST, Url:

Email alerting still works and SW is still generating tickets in ServiceNow. This is just tied to Teams. Let me find that log and hopefully it will tell me my issue.

What about hardware requirements? We recently did some changes to CPU and RAM on our current DPA deployment. Do these change at all with Server and SQL 2022?

We just updated to 2023.1.0.265 so as things stand now we cannot support SQL 2022. We probably will have to wait a month or two to update to 2023.2.1 to have the bugs worked out of that release. I also will meet with our DBA team and to discuss the Microsoft JDBC driver item. We go back quite a bit with SQL so that also…

What you need to do is create an Alert Contact. This can be found at the bottom of Users and Contacts. 

Thank you! DPA usually has been the easy update from Solarwinds. Glad it still is that way. My latest Orion update was really fun. 

I upgraded on 6/1/2023 and it looks like this issue has hit me as well. I actually was trying to update to 2023.1.1 BUT the Software forced 2023.2.1 on me. Yaay!!!

We are back on up. Thank you!!!

Holy crap., I have a support ticket open from last week when I tried the update. I just did this on the APE. I will let things sit for a few mins.

Thanks. Tried this on MPE and still no go. 

Did the update today and it forced me to install 2023.2.1. Which was ok but now None of my AppInsights for IIS are working correctly and I have three custom SAM monitors that are complaining about a user name and password so they are showing unknown. When I test these monitors it says there is a password issue. If it was a…

I was trying to install from the ISO and it opened up Orion and wanted me to install 2023.2.1. I also still have Admin service flapping on my APE.

01365978 ticket number. I called support and have been on silent hold for about 21 mins so far

So this is a PS monitor I found on here. I have not been able to get down/up to work on it so I am doing it via statistic on the monitor. 

Thank you. I made the changes and we will see what happens. I will update the thread when this runs for a few days.

I was a good tech and have a stage and prod instance of the alert and monitor setup. You are correct - They are looking to see if nothing shows up after an hour. The file is generated at 20mins after the hour but sometimes takes 15-20mins to generate. This is what I have on the alert

You have made my day. Thank you!!!

Found my issue. I was doing this test from the script editor. When I went back to the component monitor I adjusted the Execution to Remote Host and BOOM. I am getting data but I need to have the monitor let check for any XLS files that have dropped in the past 60 mins. For this one I am getting data older than 60 mins.…

Here is the script with the path and time updated. I know I can connect to this server and folders just fine. I have the Folder Stats monitor running against this node and it reports like it should. Let me know if you have any suggestions or if I completely over looked something. I am not very PowerShell smart. Thanks!

I thought I had this completed but after another discussion they clarified what they need. They are looking to monitor for the existence of a .XLS file in a folder. If the .XLS file is older than an hour send out an alert. I am back to trying to use the File Age Monitor (wildcard) or File Age Monitor Wildcard (1). I think…

That template is the winner!!! Thank you for your assistance!!!

I am going to meet with one of my team members that understands PowerShell much better than I do. I did the WINRM test from APE to Node and it works so that is not the issue. I will let you know if we get this working. We were able to do tests and run it locally on nodes but are having some issues testing from Solarwinds…

I found both of the scripts and downloaded them but I have not found the too much on the documentation side. I did have to make sure WINRM was working from polling engine to nodes (I did not address this when I installed SAM 2020.2)

So that works great with static files but can this be configured to check for file names that change? We have files generated hourly that we need to verify that they make it to a folder on an SFTP server. I setup the File Existence Monitor to check for the file names with a wild card which works but I need to see if this…

I will start there and hopefully the end users are looking for something easy.