In the realm of monitoring products, proactive monitoring usually means identifying potential issues within IT infrastructure and applications before users notice and complain and initiating actions to avoid the issue from becoming user noticeable and business impacting. Proactive monitoring means a business is continuously searching for signs that indicate a problem is about to happen.
The field of information technology has advanced at a breakneck pace in the last 20 years. Hence, it has become imperative for any business to know and adopt technologies that can make them productive and more competent at the same time. However, not all firms have the resources to expand their team of IT professionals for several reasons, particularly within small and medium-sized businesses.
It is incumbent on cloud operations teams to choose the correct type of AWS EC2 instance relative to the underlying application. The wrong choice could adversely impact business and user experience. This article walks through a customer case study where the EC2 instance choice impacted their business.
Infrastructure as code and automating deployment and scale-up/down in Azure is becoming the new normal. Solution architects and system administrators are becoming coders and scripting is becoming part of their day-to-day job, whilst in parallel a raft of vendors is providing products to try and help avoid this need to script and address the shortage of staff with those skills to script and code this now necessary functionality.
HTTP/2 (originally named HTTP/2.0) was a major revision of the HTTP network protocol used by the World Wide Web published in 2015. Indeed, those in the Citrix/EUC ecosystem may remember Marius Sandbu investigating the benefits of HTTP/2 for NetScaler, Microsoft IIS, and Storefront users back in 2015/6. HTTP/2 was the first new version of HTTP since HTTP/1.1, which itself was standardized in RFC 2068 in 1997.
You have two choices when deploying eG Enterprise: Wherever you choose to locate your eG Manager, eG Enterprise does not and will never collect data from your systems. There is never a data feed going from eG Manager to any outside system unless specifically configured by the customer and we do not incorporate any dubious call-home technologies. Before installing eG Enterprise, you will also need to consider the factors discussed in the Where to locate the eG Manager?
July 30 was SysAdminDay 2021. For most of us at work, the day was just like the day before it but for sys admins across the globe, it was a day when they felt appreciated and acknowledged. Much of what happens behind the scenes in the IT world works well and as expected only because of our IT heroes. They’re the ones, who don the jumpsuits and parachutes in the IT universe… Some are even ready with a fire truck in tow.
When the Citrix architecture moved from v6 to v7, one of the main components that was introduced in the v7 architecture was the Citrix Delivery Controller (CDC). A Citrix Delivery Controller is a server-side component that is responsible for managing user access and brokering (enabling application and desktop access) and optimizing connections. Each site will have one or more delivery controllers.
The Citrix Ready team recently recorded a podcast with eG Innovations for their Tech Fusion podcast series. Hosted by Neil C. Hughes from The Tech Blog Writer, Rachel Berry from eG Innovations’ product team, and CTP, Richard Faulkner, (Enterprise Solutions Architect, Conversant Group) discussed how eG Enterprise enhances and goes beyond native Citrix tools.
A typical SAP deployment is usually a sprawling, complex system and is one of the most critical applications an enterprise relies on to keep the business functioning, with it interacting with production, sales, dispatch, HR, and other areas of the business. Monitoring the performance and availability of SAP is therefore the key. Proactive monitoring may allow minor issues to be resolved before they become major issues.
