Transaction monitoring, also known as web application monitoring, is used to check the correct functioning of user interactions on your website. The interaction could be a simple login or all the actions that are needed to purchase a product in your webshop.
In order to monitor these user interactions you need to put them in a script that can be run again and again to check if everything still works as expected. Uptrends offers the transaction recorder (as a Chrome extension) to build a script in an easy way. Once you have recorded the script you can refine it yourself (self-service transactions) or ask Uptrends support to tune the script (full-service transactions). If you’re good at scripting, you can decide to skip the recording and put your own script into a transaction monitor right away.
When you upload a transaction recording to your Uptrends account, a transaction monitor will be created with some basic information. You will have to adjust some settings to fit your needs.
Once you’ve tested your transaction monitor and are happy with the way it works, proceed and set up alerting for it. After all, this is what it is about - to be alerted when things are not working as expected.
1. Planning your transaction monitoring
Understanding the mechanics of your transactions, the functionality you need to test, and the impact of your monitoring on your systems is a crucial part of planning your transactions.
- Get an introduction in “What is web application monitoring?"
- Learn why you should use web application monitoring
- Check if web application monitoring is the right solution for you
- Reasons why you may need help from a programmer (if you are not one)
- Map out possible transaction paths
- Decide what to test
- Caveats, tips and tricks: things to consider and watch out for when setting up your monitoring
2. Recording your transactions
Using the transaction recorder properly leads to cleaner recordings and faster monitor setup time.
- Donwload and use the transaction recorder
- Using the transaction recorder: shopping cart step-by-step tutorial
- How to choose between full-service and self-service transactions
- Manage sensitive values that were automatically added to the vault during recording
3. Testing your transaction script
Once you’ve recorded your transaction, and you’ve chosen to test the script yourself (you can also let our Support team handle your testing) you need to troubleshoot the resulting script, setup content checks if you haven’t already, and adjust the vault permissions on newly created items. Finally, you need to keep an eye on the monitor in staging mode before moving your monitor to production.
- Before testing and editing your script, you need to understand the step editor
- Steps and actions
- Page interactions: using navigate, click, hover, and set actions
- Ignore errors for optional steps and actions
- Using selectors and selector alternatives
- Testing and editing your script: