Operations | Monitoring | ITSM | DevOps | Cloud

I began working with database customers back in the day with VividCortex until it was purchased by SolarWinds. Since then, I’ve had the opportunity to work with tons of our database solution customers as an account manager and now lead our DPM renewals initiative. In these roles, I’ve helped our customers transition from VividCortex to Database Performance Monitor (DPM) and now migrate into Database Observability.

Kentik now provides network insight into Oracle Cloud Infrastructure (OCI) workloads, allowing customers to map, query, and visualize OCI, hybrid, and multi-cloud traffic and performance.

In today's digital-first landscape, maintaining the health and performance of your network is critical for the seamless operation of your business and its services. To that end, network observability has emerged as a key concept and discipline in ensuring the robustness and performance of networks. But what is network observability?

Engineering and ITOps teams have an important mission: keeping their software and digital systems performing and reliable. But as we’re about to embrace a new year full of changes, industry shifts, and AI developments, this mission is challenged by increasingly complex environments, technology alternatives, and an overwhelming number of tools available. The result? Overages, tool sprawl, and toil, which all lead to longer times to detect and resolve issues.

As applications in the cloud become more distributed and complex, the Mean Time To Resolution (MTTR) for production issues is getting longer. Modern systems are built with hundreds of distinct, ephemeral, and interconnected cloud components, which can make it exceptionally hard for engineers to understand the current state of their applications, what problems are impacting customers, and why those problems are occurring.

Most SREs and IT Ops manage Java applications without source code access or communication with AppDev teams. When applications have performance issues those SREs or IT Ops teams deploying and maintaining the infrastructure often have to prove that it is the application at fault and supply information to the app supplier which provides evidence of the issue.