I'm extremely new to WPM and SolarWinds in general. We have an issue with recorded transactions throwing a ton of false positives. Where a transaction will be down just long enough to trigger an alert and then resolve itself, usually on the next poll.
I believe this is due to the fact that the recorded transactions are configured in two different ways.
Almost all of our transactions are just "Go to this web page, enter user name and password, log in, verify that some version of text (Usually Logged in as User: etc) exists, and that means the page is up."
About 50% of these transactions have a wait time between entering the user name, the password and clicking login. Example: Enter User name > wait 5 > enter password > wait 5 > login > wait 5 > check for text
The other 50% do not. Enter User Name > Enter Password > Login > Check for Text.
When these fail, the screenshot that gets captured is of the initial login page. I'm taking a guess that the recorded transaction is not waiting long enough for the login process to actually complete depending on latency between the various environments. Is there a best practices on wait times? Should a wait be included between each step in all record transactions?
