As SF author William Gibson said, “The future is already here—it’s just not very evenly distributed.” Some IT infrastructure teams live in a future where they are resolving every issue before there are problems for end users. These teams live in a nirvana where help-desk tickets are all requesting new accounts to be created for staff who start work next week. Phone calls bring praise from line-of-business managers. Personally, I have never seen these IT teams. Maybe they exist; maybe they are just a dream. Many IT infrastructure teams work in a very different world: a world of hurt and pain, where application performance is unpredictable. The help-desk call queue sometimes spirals out of control. When the team is this deep in alligators, it can be hard to see how to drain the swamp. A crucial first step is getting the lay of the land and some idea of where the problems are coming from. The next step is to start dealing with the root causes of issues before they cause problems.
Articles Tagged with Monitoring
I just returned from a week in Las Vegas at AWS re:Invent, Amazon Web Services’ annual conference. I have either attended or watched the live stream every year for the past several years, and I am continually amazed at the number of new services and features that AWS cranks out annually. During the course of each year, I keep reading about how the other public cloud providers are gaining ground on AWS. However, I am not seeing that. Amazon is dominating with large enterprises and Fortune 500 companies. Many of the big wins from the other cloud providers are in companies looking at multicloud strategies or targeting specific workload types (e.g., Google for big data workloads).
Many IT departments view new or recently migrated XenApp/XenDesktop implementations as complete when users start accessing the production environment successfully. However, the use of a monitoring tool is often overlooked. The Virtualization Practice has published a new checklist-style white paper entitled Monitoring for Your Citrix® Infrastructure: Considerations and Checklist to help you determine how to best address this. The document provides the reader with numerous thought-provoking questions and line-item checklists without a single mention of a third-party vendor. By considering all aspects of monitoring, you are equipped to draw the best decision for your particular environment.
We live in interesting times. If I were to chart the increase in the number of customers asking for help with DevOps, that chart would look like a hockey stick, that same kind of hockey stick our CFOs are always dreaming of. If I added another line on the chart for the percentage of those companies that actually knew what DevOps was, it would be a flat line at the lower coordinates of the chart. What we are seeing is that everyone wants DevOps, but not everyone knows why or exactly what DevOps means.
Many companies use some flavor of an agile methodology today with mixed results. I have written about agile fail patterns in the past, but some companies do an excellent job of applying agile best practices yet still suffer from missed dates, botched deployments, and low quality. Why is that, you may ask? Because most agile methodologies only address the development side of the house and clearly ignore the operations side of the house. The two need to work in tandem to produce the desired results, which is the goal of DevOps.
The focus of many of my blog posts is on topics around how to be more agile. One key strategy for increasing agility is to focus on core competencies and leverage the cloud for all non-core functions. Much of the discussion about cloud services focuses on IaaS, specifically AWS versus the various private cloud solutions, but another way in which companies are achieving agility is by leveraging SaaS solutions for key operations functions.