Human operators utilizing traditional network monitoring software with methods like SNMP, ping, or flow tracking are still limited to diagnosis and triage issues within the four walls of the on-premise data center. But with increased adoption of cloud, SD-WAN and “work from anywhere,” application workloads are getting more distributed and creating network monitoring visibility gaps.

The increasing adoption of modern and cloud-native architectures is enabling enterprises with IT infrastructure that is more dynamic and ephemeral, and thus more resilient. This trend drives infrastructure monitoring tools to transition from simply “keeping the lights on” to providing advanced insights such as predictive analytics for infrastructure workload optimization. Infrastructure monitoring that was once art has become science.

Making IT operations simpler – which AIOps does by helping teams to make smarter, more informed decisions about complex monitoring and APM problems – is great. But what would be even greater is eliminating the need for IT teams to make decisions at all – a prospect known as NoOps. By automating application management to the point that human involvement is no longer necessary, NoOps offers tantalizing possibilities for the IT operations teams of the future.

To date, AIOps has been a solution first and foremost for IT operations teams. In other words, AIOps has been used primarily to help IT teams manage what happens in the post-deployment part of a CI/CD pipeline, when they need to detect and remediate issues in production environments. That doesn’t mean, however, that AIOps leaves developers out of the picture. Although the conversation surrounding AIOps hasn’t paid a lot of heed to developers so far, it’s perhaps time to change that.

Broadcom officially closed on the acquisition of AppNeta on Jan 31, 2022. This marks a new beginning for AppNeta and the Broadcom network monitoring software business. AppNeta will take the lead in our vision to enable Network Visibility Anywhere, focusing especially on operational blind spots and experience in the last mile. We aim to ensure a quality digital experience anywhere while working, transacting, communicating and automating.

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.