1. Support
  2. Knowledge Base
  3. Transactions

Transactions

We’re changing our user interface. Some info may not yet be up to date. Please check From classic to new UI.

Once you’ve decided to move forward with transaction monitoring, you may need additional information or help to get you started maintaining your monitors. Between our Academy and Knowledge Base, we have the answers you need. However, if you still have questions or need additional help, Uptrends Support is here to help you over any hurdles you may face.

We have a detailed step-by-step Academy lesson to take you through the basics all the way to transaction monitoring success.

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.

2. Recording your transactions

Using the Transaction Recorder properly leads to cleaner recordings and faster monitor setup time.

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.

All articles in this category

  • Analyzing Transaction Errors
    Sometimes things don’t work the way that we’d like or expect them to – and that includes your monitored transactions! Below you’ll learn about transaction errors and how to analyze them, so you can get everything up and running again. Check the HTML output In the event of a transaction error, the Uptrends service grabs a copy of the HTML output seen when the error was detected. This data can be a powerful tool to learn what a page looked like at the moment a problem occurred.
  • Automatic variables
    A list of automatic variables for use in Transaction/MSA monitors
  • Choosing which transactions you can or should test
    Determining which transactions you need to test with Web Application Monitoring is an important first step when it comes to setting up a successful transaction monitoring strategy. What transactions can I monitor? A better question to ask is, “What kind of transactions CAN’T I monitor with Web Application Monitoring.” Using Web Application Monitoring, you can test almost any task a user may need to perform on your website or service. That leaves you with a lot of monitoring options.
  • Content checks
    When setting up transaction monitors, you may want to consider a few things.
  • Converting existing transactions to Self-Service Transactions
    Converting your existing transaction monitors is a manual process that takes time. Learn how and if you should convert your existing monitors to the new Self-Service Transactions.
  • Exclude A/B tests from transaction requests
    A/B tests can cause errors and generate needless alerts. You can prevent unwanted alerts by telling Uptrends to exclude requests to your A/B test tool’s URL.
  • Finding selector alternatives
    Sometimes selectors don’t work, or they only work some of the time. In this article we step you through some of the common selector problems and suggested fixes.
  • Is transaction monitoring the right solution for your scenario?
    Transaction monitoring is perfect for keeping an eye on the scenarios that your users depend on, but you may want to consider some other options.
  • Managing authorizations for automatically created vault sections
    When you record a transaction, Uptrends stores your sensitive information in an automatically created section of the Uptrends Vault using default permissions. Learn how to manage authorizations for the automatically created vault items.
  • Page interactions
    Within your transaction monitor you have the option to add four different types of interactions or actions. In this article we break down the four types.
  • Switching between iframes and browser tabs
    When your transaction needs to open and interact with new tabs or embedded iframes, you may need to make alterations in your script to handle the switch back or the selectors used.
  • Transaction Monitoring caveats, tips, and tricks
    When setting up transaction monitors, you may want to consider a few things.
  • Transaction monitoring for mobile setup
    Using Uptrends Transaction Recorder, you can also test transactions for your mobile site. Learn how.
  • Transaction Recorder incognito mode
    You can improve the quality of your transaction recordings by allowing it to run in incognito mode. This can help with things like existing login sessions and cookie walls that might get in the way. To allow the recorder to run in incognito mode: Open Chrome Navigate to ‘chrome://extensions/’ View the details of the Uptrends Transaction Recorder extension On the lower half of the screen enable the option ‘Allow in incognito’
  • Transaction Recorder selector determination
    When you use the Transaction Recorder, the recorder makes the decsision of about how to identify the individual elements on the page based on several factors.
  • Transaction script review policy
    To facilitate the fast processing of the transaction scripts, we have established guidelines to keep things fair across all accounts.
  • Understanding transaction monitor credit calculations
    Learn how we determine the number of transaction credits set for your transaction.
  • Using ignore errors for optional steps and actions
    Your transaction scripts need to be able to respond to dynamic site changes. Using ignore errors gives you the control you need to insert conditional or skippable statements into your script’s steps and actions.
  • Using sensitive transaction data stored in the vault
    When you record a transaction, Uptrends stores your sensitive information in the Uptrends Vault. Learn how to access and use your sensitive data in your transaction scripts.
  • Using transaction screenshots and waterfalls
    For thorough testing of your transaction scripts and later for troubleshoot, you need to review the waterfall reports and screenshots to identify the source of errors and the health of your transaction monitoring script.
  • Using wait conditions
    When scripting your transactions, sometimes you need to instruct the monitor it needs to wait for a specific element to load before proceeding. Transaction monitoring supports three types of wait conditions
  • Working with Transaction Screenshots
    Note: Transaction Screenshots are available in the Enterprise version and Business version. When monitoring transactions it can be easy to get lost in the details of all of the data that is being communicated across a web page. To help make this task less daunting, we offer screenshots for transactions. Why use Transaction Screenshots? This option is useful when trying to track down a specific error, or if you wish to see what a particular page looked like on a specific time and day.
  • Working with Transaction Waterfalls
    Note: Transaction Waterfalls are available in the Enterprise version and Business version. What is a Transaction Waterfall? Full Page Check monitors collect all of the outgoing browser traffic that happens while the page is loaded, thus recording all images, scripts, stylesheets and other files that the browser downloads in order to display the page. This information is displayed in a chronological time sequence, forming a kind of waterfall chart (typically containing up to 100+ elements for one page).
By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.