SaaS Application Performance Monitoring, Series 2: Transactions
We have seen in the Series 1 of How To Improve the Performance of SaaS Applications using Nexthink on how Nexthink Application Experience could be leveraged to proactively monitor Page load times of Web Applications to improve user experience and application performance for increased business value.
Let us see in part 2 of this series how Nexthink could be leveraged to monitor Application Transactions
Data collection primarily helps IT teams to characterize the performance of SaaS application, this measures and improves the employee experience. Monitoring the performance of application transactions is an effective way to improve the performance of SaaS applications.
A Transaction is an employee action or event in a web application which creates business value for the company. To know if employees can get things done with the applications they use, a service manager needs enough granularity to see if the employees can perform certain actions as efficiently as possible. These are actions specific to an application, which are important to monitor because it is through these actions that the business value is produced by the application.
Monitoring the Transactions help companies:
- Identify specific issues with apps and raise the issue to the SaaS vendor for enhancement, troubleshooting or support.
- Help monitor the performance and identify issues during UAT of specific modules before the apps are put into production.
When an organization rolls out any new application, Nexthink can configure application transactions and monitor the users and identify if the performance is acceptable or further actions are required during the UAT and observe the transactions to see how it’s performing.
The first step before you monitor a transaction that can improve the performance of a SaaS application is to Configure the desired application transaction, this is how we Configure a Transaction
Here, let us see how to monitor the Transactions for the SaaS Application Salesforce Lightning.
Step 1: Navigate to the Applications tab and click on Applications overview.
Step 2: Select the Transaction duration to See the transactions of all the SaaS application.
Step 3: Here, we will be monitoring the transactions of the SaaS application Salesforce Lightning. Click on Salesforce Lightning.
Step 4: Click on Transactions tab to view all transaction details.
Step 5: On the right-hand panel, under Investigate more we can do a detailed drill down on the Transactions.
Step 6: Select the Transaction name. Here we are selecting all the transactions for investigation.
Step 7: Click on Investigate to look at the transaction details of the displayed results.
Step 8: Click on Transactions to run the investigation for the SaaS application Salesforce Lightning.
Step 9: This will display the devices, here we are selecting the device displaying the Experience level as frustrating to the user.
Step 10: This will display the devices where the users are having frustrating experience , Click on Investigate.
Step 10: Next, select Devices to run an investigation.
Step 11: Click on the device Name to look at the device view.
Step 12: Scroll down to the Applications section and hover on the one of the transactions to see the Usage, Page views and Transaction details.
Step 13: In correlation, we can see that the average transaction duration on the selected parameters is high for Salesforce Lightning.
With this we can see How To Improve the Performance of SaaS Applications using Nexthink
Using Nexthink Application Experience, we can clearly See the different transactions and the transaction duration of the application. This information helps us gather more data on the applications and understand when there is a performance issue.
This transaction information can also pull up other devices facing similar issues, the conclusion of this can be sent to the Applications team for further analysis and investigation.
The post How To Improve the Performance of SaaS Applications using Nexthink – Application Transactions appeared first on Nexthink.