Want To Monitor Dynamic Web Transactions? Now You Can With Improved Java and .NET Monitoring, APM Insight
If you're an application owner responsible for tracking the performance of your web apps, the one thing that would be on top on your agenda is to make sure your customers can transact all the time without abandoning the transaction, and we are sure Site24x7 APM Insight is your perfect monitoring companion assisting you in keeping a hawk eye on how your applications perform end-to-end.
However, when it comes to tracking transactions, you would see that in many cases, the URLs related to a transaction are~dynamic.~You must have always thought, getting cumulative~performance stats on such applications is always a herculean task. Why? Read along to find out.
Dynamic Web Transactions
Dynamic web transactions are web transactions within an application having a single URL but get appended with unique alpha numeric identifiers every time they are invoked, making the web transaction name itself look different. Keeping track of individual URLs as a single entity is painstaking and cumbersome.
Lets now look at an example of dynamic web transactions within an application.~Every time a transaction namely,~www.demoapplicationfortest/additem.do~is triggered~you would get unique web transaction URLs like:
www.demoapplicationfortest/1324/additem.do
www.demoapplicationfortest/135456/additem.do
www.demoapplicationfortest/additem.so/<unique id>....and so on.
Keep in mind that it is the same back-end code that is being called every time. No matter what the format of the URL is, the transaction that needs to be monitored would have to be ~- www.demoapplicationfortest.com/additem.do.
Whats wrong with individual URL monitoring?
When URLs are not properly grouped, dynamic web transactions~might~generate large amount of data~ to Site24x7, now this data reduces the effectiveness of the monitoring metrics that you see in your Site24x7 dashboard because of the distributed nature of the URLs. Such was the case initially monitoring dynamic applications using~Site24x7 APM Insight,~ each and every web request was tracked as a unique transaction, making it difficult for you to measure the core metrics, such as:
- Number of Requests
- Throughput
- Average Response Time over a period of time
- Minimum Response Time
- Max Response Time and more.
This defeats the whole purpose of performance monitoring of the application as you get distributed statistics and monitoring becomes impossible. But all that is a thing of the past with this update.
Grouping of Similar Transactions
We have come up with a new feature in APM Insight -~Group Similar Transactions.~This allows you to clearly specify your web URL pattern along with regular expression of the unique~identifier, not just that, you can also specify a name to assign to this group of unique URLs for easy identification.
Thereby~:
www.demoapplicationfortest/1324/additem.do
www.demoapplicationfortest/135456/additem.do
www.demoapplicationfortest/additem.do/<unique id>
Can be grouped together as a single~entity~and monitored together to give you that~cumulative performance~know-how~of the application which was missing all along, totally hassle free.
How to Group Similar Transactions
Its simple, since these are application specific and customer specific transactions, the customers have to configure it in the~transaction_merge_patterns.conf. Any regular expression grouping can be done. For more information on the exact steps involved in the configuration, refer our~help documentation.~
So what are you waiting for? Experience these latest features right away and let us know what you think? Sign up for a 30 days free trial.
Watch your application performance monitoring superhero in action.