marcrobinson · Observability Detective · ✭✭✭✭✭

This is expected behavior for the OOTB alerts. They provide baselines that you can copy and modify to meet your needs. 

That is a keep alive entry in the log file. You are modifying the SQL db and the config wiz has is still running. I ran into that with the 2020.2.1 HF2 upgrade. The sql portion lasted hours, it has to do with your db in particular. That is what I learned from my ticket in December. My advice - let it run. Get a coffee, or…

I am curious to hear what others say, in particular those with larger environments that include multiple modules and scalability servers (ape's and awe's). 

Hello @"vinay.by" I agree. I believe things like the .net changes require rewrites, as do accommodating wmi variations in windows. This question came up recently and I don't recall seeing a specific article about how/when components are upgraded. Thank you Marc

Create an external node, you could name it "Website Monitoring" then assign the template with the https/ssl expiration components (just keep adding them for each site/cert to that template) to that external node. 

I havent run into this since 11.5.3 and 12.x. We broke the link by removing all view limitations and creating them on each dashboard. There was an article on how to remove it. I think it was called :Modifying the limitations of copy view affects the original view. Two posts on this added below.…

Just from what you said, the key phrase for me was "the ip becomes used." I am guessing what happened - When status changed from reserved to used, it was due to normal IPAM scanning. This updated the information for the IP. When the device stopped replying; the change to transient and then available was made per normal…

When you say you havent used NPM for a while, do you mean that you click search in an inactive session from earlier and perform the search or open a new tab/browser sessions, log into NPM, and then search? I have noticed timeouts from the former, but not when you log in or have an active session. 

I have had good luck with the callback feature for support. Please create the ticket first, call in, enter ticket# when prompted, and unfortunately wait about 30 minutes for the call back prompt. @"danielleh" - please ask if the support team can add the call back as an initial option in the support menu. They typically…

Open a ticket. if you have a large environment with lots of data, the config wiz can take hours. And more hours. Check the config wiz log file and look for at this document:…

I believe the tags are only set/created/applied when you edit the check itself. Secondly - go to the support option in the pingdom interface. there is an method to submit a ticket. choose technical support and select pingdom from the drop down product list. 

If you want it to have it contain information related to that app - consider creating a custom table widget, or a perfstack report and add the perfstack to the page.

check this thread. https://thwack.solarwinds.com/t5/NPM-Documents/Orion-URLs-for-Firewall-Whitelisting/ta-p/613706

Try the percent symbol. 

Mark, Thanks for keeping us posted on this issue. I am still sitting on the sidelines waiting for the hotfixes to cool down. I have a multi-module, multipoller installation and fear that I will fall into the same pain that you are experiencing. Especially with the new installer, which I love otherwise. Thanks Marc Robinson

@"deiberts" Good catch on the black box monitors. I checked another insight app - active directory and noticed the same upward shift in chart data. 

Hey @"johnwilly" That is a great question. Unfortunately, not the best answer. If you use default settings then you cannot name the disappeared AP. I learned that the db has a setting to remove them by default. You will need to go to YourOrionServer/.../Global.aspx and scroll to the Wireless section. There is an entry call…

in your code sample, it looks like there is a space at the end, between the swql variable and the two closing brackets. I can't see any other issue, especially since it appeared to grab the Manual_Scan job name in your test. We are still doing OK using the TOP 1 filter for the Discovery Successful and Discovery Failed…

I’d recommend getting current if you can – just pay special attention to the windows OS version requirements and the sql version requirements. Also – lots of shiny new toys, er features, since 12.0. Good Luck! Marc

sorry for not replying sooner. There is a table that stores the configs with xml wrappers.I believe that also has the template name. I will continue to poke around for the template and post what I find.

Creating a feature request for loggly still appears disabled. Here is the same view for SAM, with the links to submit a feature request.

Glad I could help a bit. If I can fix the user defined swql variable, I will post it. I do not believe that this one is in the named variable lists. Then you can add it to your email notifications. 

I agree with Superfly99. I have stopped my planned upgrade until this settles down. IPAM is too highly used to chance it. But I REALLY want NPM 12.2 and the new SAM and NCM updates…. This will get fixed, so wait if you can.

I cannot select it as an option though. See image below, Loggly feature request forum is grayed out.

Here is the bad version. 

Thanks for the tip. I was able to notice that the template was not logging in. I switched it from normal to always for authenticate/login. THat did the trick.

I do plan to upgrade to NPM 12.2. But I am waiting for next round of fixes for IPAM 4.6 to get posted. Here is that thread: IPAM 4.6 is broken .

Currently testing an alert based on the event that is logged when a thin ap disappears. THis is NPM 12.3. There is no reset condition, as it logs disappearances only. The logic is shown below. This has worked pretty good so far, but I have not completely switched to it.

Hey lynchnigel, Good Catch, and thanks for that tip! I never even thought about the complex conditions. And I am at NPM 11.5.3 (soon to be 12). THe alert I am using was a Wireless Access point. See below, since its a WAP alert, targeting the thin AP's, your solution should be good. I will test and post back my results.

I think mute and perfstack were released in orion 2017.1 and NPM 12.1. I was able to find release notes for NPM 12.1: NPM 12.1 Release Notes . Looks like these features were released together.