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.
If you are new to web application/transaction monitoring, you will find some background knowledge in the following articles and lessons:
- 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
2. 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. You also may have to involve other teams at your company to set up transaction monitoring.
- 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
- Reasons why you may need help from other teams at your company
3. Recording your transactions
Using the transaction recorder properly leads to cleaner recordings and faster monitor setup time.
- Download and use the transaction recorder
- Follow the shopping cart step-by-step tutorial to learn how to use the transaction recorder
- Choose between full-service and self-service transactions
- Convert existing transactions to self-service transactions
4. Editing and 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.
To learn about the editor, steps and actions check out Understanding the step editor
Actions are at the core of transactions. Learn more about them:
In the exercise Testing and editing your script, find out about the Test now functionality, how to handle dynamic IDs and timeout errors. The lesson also contains a Testing checklist.
A few other things you may have to deal with, depending on your setup and transactions:
Manage sensitive values that were automatically added to the vault during recording
Manage vault authorizations (automatically created sections)
Transaction monitoring for mobile setup
Working with a shadow DOM in your transaction
Working with SMS-based 2FA or one-time password-based 2FA in your transaction
Adding extra metrics such as Core Web Vitals and W3C navigation timings, to your transaction results.
Bypass or override the default DNS system by using a DNS bypass in your transaction
5. Results of transaction monitoring
Once your transactions are monitored, you’ll receive feedback. There are a number of sources you can look into to find out what is going wrong, when things go wrong.
When the transaction monitoring does not work out as expected, here are a few things to check: