I'm looking for any tips and general discussion on the topic of trying to eliminate "false positive" alerts from monitoring, while always alerting when there actually are incidents.
For example with one site that we're monitoring, there was a problem that we were receiving false positives because the site kept changing constantly, and some DOM locators from the old script didn't match after the change. Or then a string we were verifying against wasn't found anymore because a different wording was used after a site upgrade. But after trying to make the string verification more general, there was a time period when an attempted search function on the site failed 100 % of the time, but no alerts were sent because the string we used was also found on the previous page.
So basically it's a question of balancing between detailed and reliable vs. dynamic and general. I've found that some string verification usually is needed, because if I just wait for "Page Complete", I don't really know what I'm downloading.
If you've struggled with similar topics and perhaps even found some solutions, please do share them! Or any tips in general for verifying that the site's content was correct.
Answer by Benjamin W. ·
Many customers encounter similar situations, and I'm afraid I don't think there's a silver bullet that solves that problem.
The approach I've seen work best so far is to include whatever monitoring solution you use in the application's release process, so that whenever a new version of your web page or application is built, the monitoring script is also tested as part of general testing, and if it fails, the script is adapted to the new version as part of the release process. This ensures that your application and the monitoring scripts are in sync. This is independent of which technology you're using.
It will probably not solve every problem you'll face (like the example of the search function you mentioned), but it will reduce the number of false alerts.
This is assuming you can control the application's release cycle of course.
As a general note, I'd recommend using string verification for exactly the reason you mentioned.
Answer by Mark B. ·
Please see if there are any tips that help here - https://community.dynatrace.com/community/display/...