eSignature Licitness for Business Transaction Management in Mexico

How to eSign a document: eSignature licitness for Business Transaction Management in Mexico

welcome back to SRE with Ben today we are going to talk about an exciting topic lab dynamics that is business transactions let's get started to understand what a business transaction is first let's understand what is a transaction in a web application any web application you take there are certain functionalities that the web application offers right like your login order checkout or search for an order so these functionalities have a direct impact on your business since um if a functionality like a login is not working then your user is not able to log into your application and place orders and if he's not placing orders your business is not making any money that is a direct impact to your business such functions which have a direct impact on your business are considered as business transactions now let's learn about how to monitor business transactions using App d by taking a use case let me consider myself as the owner of a JPEG store and this is my web application and I have certain functionalities this application offers that is to order a bits from online store so I have one functionality that is to sign into the store then I have various other capabilities to to view pens and to place orders on them so I'm going to place order and I'm going to do checkout print also I can see my account and what are the orders that I have placed now I want app Dynamics to be used to monitor this application and monitor these crucial transactions for me login and check out order so let me go ahead and do that I have already instrumented a Java app engine for this application if you have not watched that video I recommend you watch it so that the application gets connected to my app Dynamics Fund product once my Java agent is connected to my app Dynamics controller this is the landing page for me once I open the application so you can see here by default app Dynamics as detected how many nodes I have and any back-ends so backend is a database in my case it's a in-memory database so to view business transactions you will have to go and click here on the left side business transactions your appd lists a set of transactions that it has Auto detected and I can see only one transaction has been listed here that is jpit store slash actions but if you see in my application there is differentiation for each activity for example if I go and check out something I can see in my transaction it is cut action this jpeg store slash actions is not very descriptive so I am unable to see what are the functionalities that is happening in my application basically I am unable to differentiate between the crucial transactions why is that so that is because in app Dynamics when you enable auto transaction detection app Dynamics always considered the first two elements of your URI so in my case the first two elements of my URI after my domain is jpeg store slash actions that is why appdynamics is grouping all these transactions regardless of what transaction it is whether it is order or card or catalog or any transaction it is grouping it under jpeg store slash actions this is not an ideal case for me so let me go ahead and first configure app Dynamics to capture transactions that I want to do that all you have to do is either click on configure your and it will take you to a section called transaction deduction under instrumentation or you can scroll down on the left left bar and click on configuration and click on instrumentation and go to transaction reduction so here you have a list of transaction deduction rules that have been configured for various types of app pages for example java.net PHP Python and Etc so first let me go ahead and identify which is the auto Discovery rule that is capturing my transactions and grouping it in my case it is this rule so I'm going to open it and I am going to edit this so if I see in the role configuration when I scroll down I can see under servlet Section the the transaction configuration is use the first two segments of the URL right but for me the first two segments is not very useful information so so I'm going to change it to use first three segments of the URL since I want to capture the information after these two segments because this is what is making sense to me this is how you can change the default behavior of your business transaction capturing mode and I'm going to click on Save now once I changed the default Behavior so three segments and when I generated some load up on my application I can see now um all the business transactions that I required for me have been captured so I can see it's capturing the third segment also so now it's making more sense to me so I can see what is the order Transaction what is the card transaction and what is the catalog transaction now it is very clear for me how each of my business transaction is performing right so I can see what is the response time of my transaction and what is the number of calls per minute any errors any slow transactions and things like that so this can give me a gist of how my application is performing and how the various business transactions are performing right so why does appd default transaction reduction to two segments because in an Enterprise application your url can have n number of uras for example you can have order slash one order slash two based on the unique ID of the model if empty tries to capture the complete URL there are going to be any number of transactions captured and it will be very difficult to identify which transaction is needed for you and which is not needed for you because of that app they always uses to capture first two segments of the URL as a transaction now let's go and understand what information appd is capturing for any deducted transaction so for that let me go and double click on the business transaction and I can see in the dashboard there is a flow map showing which node this transaction is initiated from and what is the backend it's using this is an in-memory database I can see uh what is the number of calls and what is the number of calls per minute what is the response time for this transaction and what is the header rate and if I scroll on the right side I can see something called as a transaction scorecard this gives basic details of the transaction on how it is performing and if there are any slow calls or any stall calls or any errors so that type of information can be seen from your as an overview now I can see my normal is not 100 and I can see there are some very slow calls so let me go ahead and investigate it why uh transactions are slow so how do you investigate why your business transaction is slow or why your application is performing slow this is where we get to the part of application Performance Management and how app Dynamics is helpful for you for us so our update app agent works is it injects itself into the application code and it tracks the application code from end to end from when the thread starts to when it ends every time any code block is executed in an application the appd agent knows about it it's like in god mode what it does is it captures something called as a transaction snapshot periodically that can be configured as well for example anytime a login transaction is happening the active agent is captured during those transactions snapshot and sending it to app Dynamics so to understand why my business transaction is slow first let me go and investigate our transaction snapshot for that let me go ahead and click on transaction snapshots here I can see a list of transactions captions which have been captured by the FD agent and sent to controller and if you see this indicates that this snapshot this transaction was normal and this indicates very slow so let me go ahead and verify it that have the execution time what is the latency what is the URL on which this business transaction happened and what is the tire and which node so I can see there is one transaction with the marker saying it's very slow so let me go ahead and investigate it and also I see the execution time is higher than usual hence app Dynamics has marked it as very slow to investigate it double click on the transaction here I can see a brief about what is the transaction and what are the backends which node it's running on and on the left side I can see potential issues that might be causing the transaction to take time and what is the response time of each call for example these are all Java method invocations or class invocations so I can see what is the response time of each of those class invocation so I can see a database call also taking too much time now I want to see how this transaction happens and which at which exact point the issue is happening for that I'll have to click on print down once you click on drill down you will land in a section called as the call graph this is the complete trace of your application request it gives you a detailed snapshot of a single transaction in your application from start to end it also gives details regarding your function calls database calls and external service calls Etc we will be going through the call graph in details in the coming sections that's it for today's video thank you for watching happy learning