Patches, fixes, Fix Packs, FPs, SPs, updates, upgrades. Whatever you call them, incremental updates and fixes may be one of the oldest pain points for software users everywhere. Fans of online action role-playing game Fallout 76 will know about this. A 50GB day one patch that deleted the 100GB install file, followed by another patch of similar size the next day was a major source of frustration for users and contributed to a very hostile reception and disastrous sales compared to previous versions. This is an issue that reaches beyond the apocalyptic wastelands of West Virginia. Every couple of days, I watch applications on my phone update with 20MB patches and I wonder what do these contain and how is this effecting my phone’s performance over time?
As an Application Delivery Manager, you know how common updates and patches are, especially given the increasing ubiquity of cloud-based applications. You know that the interconnectedness and complexity of your network means it is critical that patches are installed successfully. You also know that few major patches and upgrades are completed without issues. Identifying these issues can be a real nightmare, especially considering the oft conflicting prerequisites and requirements for each update. Early detection and identification of such issues is one of the pillars of our pre-emptive alerting and escalation service Kemp 360 Vision. Also, a successful install of an individual component is not a success for you if it causes bottlenecks or performance issues for your entire network. Kemp 360 Vision leverages its overview of the entire landscape and Kemp’s experience with these issues to help you to make updates and changes a success for your entire network.
For example, imagine that you need to update a Microsoft Azure service. You do so and do not notice any issues during the installation. You consider the update a success. However, Kemp 360 Vision is constantly monitoring your environment and as part of this monitoring, it notices that the CPU usage is very high on your Microsoft Active Directory server. If not corrected, this will degrade the performance and application experience for any applications that use the server for authentication. Kemp contacts you and asks you to check the server resources and the increased load. You realize that the update earlier in the day must be the cause of the increased load. You roll back the update before your applications’ experience is degraded. Once you have addressed the problematic update, you can install without any issue, safe in the knowledgethat Kemp will alert you if it causes further issues.
If you would like to start monitoring updates proactively, visit kemp.ax/kemp360/vision.