You know that observability plays a crucial role in helping to manage today’s distributed, cloud-native, microservices-based applications. But you may be surprised to learn that – despite its close association with modern applications – observability as a concept was born more than a half-century ago. Its origins stretch all the way back to the late 1950s, long before anyone was talking about microservices and the cloud.
Broadcom Software is dedicated to ensuring you are on the latest software releases with the most critical fixes, security enhancements, and integrations. That’s why Broadcom Support has developed a DX Unified Infrastructure Management (DX UIM) Designated Weekend Upgrade Program to assist you with a successful upgrade to DX UIM 20.4.
As an idea conceived by Gartner four years ago, AIOps is already a mature practice. But it is also one that continues to evolve as businesses turn to AIOps to support new use cases, and as AIOps vendors build better and more efficient AIOps tools. That fact begs the questions: what’s next for AIOps? What are the relevant trends that will shape the future of AIOps over the next several years, and how will AIOps use cases evolve going forward?
In my prior blog, Continuous Service Virtualization, Part 1: Introduction and Best Practices, we offered an introduction to continuous service virtualization (SV) and discussed some key best practices. In this, the second and final post in the series, we will discuss the continuous SV lifecycle and how it helps to optimize DevOps and the continuous integration/continuous delivery (CI/CD) pipeline.
Service virtualization (SV) has evolved as a popular technique and technology over the last decade. Traditionally, SV has primarily been used by testers to simulate other application components that the application under test interacts with. Typically, virtual services have been created and maintained by center of excellence (COE) teams.
As time progresses and competition grows, being “good enough” means that you may be falling behind. Engineers will discover new ways to solve problems, which will enable rapid increases in availability and scalability. With these increases comes more complexity and the generation of more data. Rather than just monitoring the new data and letting the old data sit there collecting dust, you should consider using it to gain maximum insights into your environment.
By now, you’ve likely heard of AIOps, a technique that promises to inject new levels of efficiency into IT operations with the help of AI and machine learning. But what, exactly, does AIOps mean in practice? Which specific use cases can IT organizations enable or improve with the help of AIOps? Those may be more difficult questions to answer if you have yet to see AIOps at work in your organization.
Kubernetes has become a fixture in production for most IT Operations teams. The VMware “State of Kubernetes 2021 Report” shows a distinct shift towards a reliance on Kubernetes, with almost two thirds of respondents now saying they use it in production. Companies with over 500 developers are driving this adoption, with 78% reporting that they run mostly- or all-containerized workloads in production.
The process of monitoring servers and applications has undergone many transformations throughout the years. When it began, the main question was whether the server was up or down. Now, monitoring helps answer questions about the internal state of an application and infer its status (also called white box monitoring). Monitoring today's complex infrastructure systems can be just as much an art as a technical skill.
Today, IT operations teams have to process large volumes of events or alarms in near real-time in order to protect service levels, stay competitive, and deliver a great experience to customers. If it takes too long for teams to spot and repair issues, an organization runs the risk of significant business service downtime, SLA penalties, and brand reputation damages. As IT landscapes continue to grow in scale and complexity, guarding against these risks becomes increasingly difficult.
When we talk about observability, we tend to focus first and foremost on the metrics, logs, and traces that you can collect from applications – such as request rates, error rates, and request duration. Infrastructure-level metrics, like CPU and memory utilization, might factor into the discussion as well. Here’s a third category of critical observability insights that teams tend to overlook: the network.
The term Site Reliability Engineer (SRE) first appeared in Google in the early 2000s. In Google’s 2016 SRE Book, Benjamin Treynor Sloss wrote that, generally speaking, “an SRE team is responsible for the availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of their service(s).” This means that the SRE teams at Google decide how a system should run in production as well as how to make it run that way.
You’ve heard of observability, which has fast become one of the IT industry’s buzzwords du jour. But what about actionability, or the ability to translate observability into meaningful action? The latter term may not be a trending buzzword (not yet) – indeed, “actionability” perhaps sounds almost boring – but it’s just as essential as observability in managing complex, cloud-native environments.
The National Retail Federation forecasted historic holidays sales this 2021 season, as retailers grappled with high volumes of in-store and digital traffic, along with a need for full visibility into the user experience. They turned to monitoring their Point-of-Sale (POS) systems for key analytics that revealed unique, real-time details about what customers were experiencing.
What comes first – observability or AIOps? Can you achieve observability without AIOps? Do you need AIOps if you already have an observability solution in place? These are all questions that any team considering AIOps will want to answer in order to determine the real-world value that AIOps tools stand to offer.
