I wanted to see if anyone in community has had an issue like this.
1. Open alert manager.
2. create an alert. Setup up parameters.
3. On the Trigger condition email. Click insert variable, type in the search box a variable name and have the loading spin forever, or have it return something other than what you have searched for.
After some time passes by, you notice the site getting slow, and eventually hang and become non-responsive. You RDP to you primary server to find it either not responding or responding but extremely slow. You open task manager to find swis v3 pinned your cpu at 100% and has used over 98% of the servers ram. Practically grinding your server to a halt. Our server has 24 cores at 2.8 ghrz, and over 30 gigs of ram. It has one fiber connection at 10 gigs. And just doing a variable search managed to peg out even a strong server as this.
When we dig into the system logs for swis v3, we find a massive expansive query triggered every time you click search on the variable field. And this query loops until it kills swis v3.
Spoke with 4 SW tech's.. couldn't find the cause. Went through 2 application engineers and nothing. Keep in mind, the server isn't logging system logs properly. And has many other issues but this one being the most critical as it has rendered our alert manager and web report writer useless. And those are core components of npm.
Would love to get insight from any, including SW dev's since this case is with them currently.
Thanks!
