jklundy · IT Consultant · ✭✭✭✭✭

Jeff - the WPM issue I am having is not mentioned in the 2023.2.1 release notes. In addition to the flapping alerts from WPM mentioned above, I am seeing significantly increased average transaction times. Which then causes lots of warning/critical alarms in addition to false down alarms. The player load % also increases…

Are you talking about the number of worker processes now defined in AgentSettings.dat? numberOfWorkerProcesses I have that set to 15 - which is what it was before the upgrade. There are 15 accounts in local users, and all are in the SEUM-Users group.

Unfortunately it doesn't look like the HF has the fix for WPM flapping transactions or the average duration of the transactions increasing significantly (250% in my case). At least according to the release notes.

We are experiencing the WPM issue as well. Interesting that they told you (2 weeks ago based on the timestamp of your posting) there was a known bug, but so far they have said nothing to us. We don't have issues with alerting - other than the flapping of the WPM transactions. Are you able so share the ticket #? Thanks

thanks for looking!

I'm looking to do the same thing. 1) the Analyzer Pack is just NPM and NTA. It does great for monitoring bandwidth utilization, but not available bandwidth. 2) WAN killer has been deprecated. 3) I am not sure about IpMonitor. It seems like just a scaled down version of NPM.

I have 3 more features I would like to see implemented. 1) When editing an existing recording (say to update a password), when saving back to Orion, don't overwrite manually adjusted step thresholds. Even better would be to have a way to update text fields (e.g. username/password) directly in the transaction monitor rather…

Fortinet Firewalls

As I am planning to update to 2020.2.5 tomorrow I was browsing Thwack for any issues. I am still on 2020.2.4 and received that error.

What about sftpsupport.solarwinds.com for uploading diagnostics? Customerportal needed for anything? In the Core above, do those URLs include what is necessary to populate the updates available in "My Orion Deployment"? Kevin

Thanks. Off the top of my head I don't think that will work as I don't *think* Appinsight applications are treated like a regular template. But I will go look.

Awesome JVB! Thanks for that. I never would have stumbled upon that process.

The password is not in clear text in the file. It is a simple feature that SW should bring back. Another feature - the ability to ignore certificate errors - should be brought back.

Thank you both! I was just concerned it was more than 1 table. Yay for simplicity!

Curious why you say discoveries is not the answer? It works for us. Just wondering if it's causing a problem that I am not aware of. I divide our network into ~ 1/7 pieces based on IP ranges and scan each segment 1x week.

You can do some of this now. For windows of time that you never want alerts to fire (off business hours), you can define a schedule in the alert itself. For example in the "Alert me when a transaction step goes down", you can set Time of Day. For deployment, you can manually "unmanage" the monitor in the Manage Transaction…

It is setup to automatically monitor based on my defined monitoring settings. My Monitoring settings are set to not include the current Appinsights. Unfortunately the upgrade to SAM 6.9 added the AD and enabled it. That is the problem.

This is awesome. I don't suppose you have created a template for SAM and WPM have you? Kevin

I know this is several years old, but would this still work in the latest versions? Or is there now a better way?

I just ran into a missing feature that is big for us. In the deprecated recorder, we could open an existing recording and edit certain actions - things like edit text entry. So when a password changes, I could open the recording go to the step and change the password, then save the recording. With the new recorder, I have…

Conditional blocks - We use these to account for things like a password expiration warning popup. There also needs to be a way to ignore certificate warnings. It won't even attempt to record if it detects a certificate error. Kevin