{"id":1227,"date":"2019-02-15T16:51:50","date_gmt":"2019-02-15T07:51:50","guid":{"rendered":"https:\/\/jennifersoft.com\/en\/?p=1227"},"modified":"2019-07-16T11:49:57","modified_gmt":"2019-07-16T02:49:57","slug":"what-is-deployment-indicator","status":"publish","type":"post","link":"https:\/\/jennifersoft.com\/en\/blog\/tech\/what-is-deployment-indicator\/","title":{"rendered":"What is Deployment Indicator"},"content":{"rendered":"\n

When a new version of the code is deployed in production, JENNIFER can automatically<\/strong> detect this change and display the changed resource in the deployment.  A vertical line will be drawn on the Real-Time X-View. This line is referred to as the deployment indicator. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

How To use Deployment Indicator<\/h2>\n\n\n\n

The deployment indicator can be used to analyze pre and post-deployment issues as well as isolating or pinpoint the performance problem location. Since X-View visualizes all the transactions in Real-Time, adding the deploying indicator will make it easier to know if the new code is causing a problem or no. <\/p>\n\n\n\n

Let us consider the following scenario, a new version of the application is deployed, and shortly after performance issues starts to appear. <\/p>\n\n\n\n

By examining JENNIFER Real-Time X-View, we can see that a deployment took place around 2:17 pm.<\/strong> and a single WAR file was deployed as the number on top of the deployment indicator shows.<\/p>\n\n\n\n

\"\"

<\/figcaption><\/figure>\n\n\n\n

Before the new code was deployment, the transactions distribution on X-View was normal and average response time as around 6 seconds. However, after the new code is deployed, we can see that the average response time increased to about 25 seconds, and several exceptions were occurring. <\/p>\n\n\n\n

Interacting with the Deployment Indicator<\/h2>\n\n\n\n

Double clicking on the deployment indicator will show the Source Code (resource) history pop-up window. This window contains additional details about the deployment such as Deployment Date\/Time, Agent, Deployed file(s) name as well size. Selecting a file from the deploy list will show the changed resources.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

In the previous image, we can see that inventory_manager.war <\/strong> was deployed to IHotel<\/strong> instance on the system. JENNIFER automatically detected that this deployed contains 2 new Java Classes: AppSetting<\/strong> and InvUtil<\/strong> as well as modified resources, the InventoryManager<\/strong>, along with their source code. This information can be extremely useful in pinpoint the root cause of the problem, comparing this information with X-View transaction and Events data, we can see that most errors were thrown from the InventoryManager and InvUtil.<\/p>\n\n\n\n

Source Code (resource) History<\/h2>\n\n\n\n

The source code (resources) history menu is located in the Analysis perspective of JENNIFER, you can use it to analyze all past deployment. This screen will allow you to search for deployment that took place in a specific month. <\/p>\n\n\n\n

In the following image, we can see that 2 deployments<\/strong> took place on the 5th of August 2018<\/strong>. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Source Code Difference<\/h2>\n\n\n\n

JENNIFER has the ability to show the difference in the source code compare to the previous deployment. In order to use this functionality, you will need to enable the Souce Code Diff Plugin<\/strong>. The plugin is already shipped with JENNIFER and the code of the plugin is available at our Github Repository<\/a>.<\/p>\n\n\n\n

To enable the plugin,<\/p>\n\n\n\n