This submit was at first published on November 27, 2017. It was current with information and facts on the New Relic cluster explorer and utilizing the New Relic platform to keep track of Kubernetes environments.
Around the very last handful of many years, Kubernetes has emerged as the de facto conventional for orchestrating and handling software containers. Just about all the considerable players in the cloud-native application space—many of them fierce competitors—have thrown their guidance guiding Kubernetes as an industry normal. Measured on developer help, Kubernetes’ journey more than the past three years—from 1st community overall look to serving as the most important subject at an celebration attracting more than 7,000 attendees (KubeCon + CloudNativeCon)—has been only spectacular.
Here at New Relic, the Kubernetes tale boils down to a few of extremely strategic factors. Initially, we believe that that for all of its achievement to date, Kubernetes is actually—and amazingly—still in its early journey towards reaching its total potential. Tomorrow’s Kubernetes environments will operate at a scale that will dwarf what we see these days. As Kubernetes environments carry on to scale, they will also proceed to get a lot more complex—and to existing even larger problems for initiatives to check their effectiveness and overall health.
Second, numerous of our consumers inform us they see tremendous worth in leveraging the New Relic platform to changeover to and operate their software workloads in Kubernetes. So we have been doing the job really hard to grow and upgrade the New Relic system with a new era of monitoring equipment intended for Kubernetes environments. These abilities will support our prospects to keep moving promptly and to act with self esteem when they adopt Kubernetes to control and orchestrate their containerized workloads.
New Relic and Kubernetes: A potent pairing
Most companies that deploy Kubernetes environments today share the identical simple aim: To improve the rewards of jogging containerized programs, at virtually any scale, by the use of automation, workload orchestration, and other enabling technologies. It is hard to overstate the relevance of orchestration in common, and Kubernetes in distinct, in achieving this purpose. Without the need of these abilities, the sheer complexity of managing and optimizing containerized workloads, microservices certification, and relevant innovations—especially when deployed at scale—might quickly outweigh their advantages.
Even though Kubernetes excels at abstracting away a great deal of the toil associated with running containerized workloads, it also introduces some complexities of its own. The Kubernetes surroundings features an added layer that will come into perform among the application and the underlying infrastructure. The obstacle of monitoring and protecting the effectiveness and wellness of these Kubernetes environments, or of troubleshooting concerns when they happen, can be daunting—especially as businesses deploy these environments at significant scale.
This is in which the New Relic platform enters the photograph as a potent and uniquely capable complement for today’s Kubernetes environments. New Relic is all in on Kubernetes, which is why we have been steadily growing and upgrading our potential to instrument, observe, and help entire observability across Kubernetes environments. This contains offering you the capacity to transfer rapidly and effortlessly from significant-stage, holistic sights of the effectiveness and wellness of Kubernetes clusters, down to the node, container, and application-stage visibility needed to recognize and troubleshoot performance troubles. It also includes the means to instrument and observe Kubernetes infrastructure alongside apps, which critical for comprehension dependencies and isolating potential performance problems.
Using New Relic to obtain conclusion-to-end Kubernetes monitoring
With that in thoughts, we’d like to introduce you to some of the most strong capabilities at the moment remaining introduced in the New Relic platform for checking Kubernetes purposes and resolving effectiveness troubles in these environments. In certain, we’ll reveal how to use the Kubernetes Downward API to surface Kubernetes-distinct metadata and then how to use the New Relic APM agent API to tie this metadata into APM in purchase to explore efficiency concerns and troubleshoot application transaction errors.
The relevance of an close-to-finish look at
By design, programs usually are not mindful of whether or not they’re running in a container or on an orchestration system. A Java world-wide-web software, for case in point, doesn’t have any particular code paths that get executed only when managing inside of a Docker container on a Kubernetes cluster. This is a key benefit of containers (and container orchestration engines): your software and its company logic are decoupled from the distinct particulars of its runtime surroundings. If you ever have to change the fundamental infrastructure to a new container runtime or Linux version, you won’t have to fully…