![]() Now that the content pack is ready, and your agent is installed and configured on your IIS servers you are set to start looking at IIS response times. The following kb is referenced, and a great place to go. Figure 1: Install Microsoft – IIS content packīe sure to pay attention to the page after this as it has important details about getting the right metrics out of IIS. ![]() The best way to handle this is to install the IIS content pack available on the content pack market place, and to install the vRealize Log Insight agent on your IIS servers. We know that IIS stores response time information in a log file. Let’s start by looking at a consumer facing web application built on top of Microsoft IIS. For your web application the same concept, a set of web servers patched and another unpatched. For Horizon you will have two desktop pools one with all the patches and one without. With both scenarios a pool concept can be leveraged to achieve your goals. Once we have that we can compare that baseline to a newly patched system. Which is any system that is currently unpatched. To get started with this you will need a baseline system. Below we will go through two examples of how to measure the impact. The first question to ask is, does my application have response time data available? If yes, how is that data presented or accessed? If the answer is yes again, then getting that data into the right tool set and a little analysis is all you need. Monitoring the application impact is going to vary from application to application. Are you using Horizon Desktops or Published Applications for Healthcare providers? You might ask yourselves has their experience changed with patching? What about consumer facing web services, are they just as speedy as they used to be, or has there been an increase in response times with patching? But answering questions like how are my users impacted by this is an extremely important part of the equation. ![]() The impact of these patches will vary for each use case and application. In addition to vRealize Operations we can leverage Log Insight and Wave Front to understand what the impact is on applications as well. Though the situation around these patches continues to evolve let’s build upon gauging the infrastructure impact and move deeper into the stack. In a recent post we’ve discussed how to leverage vRealize Operations to assess the performance & capacity impact of the Spectre and Meltdown patches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |