New Relic is extending its capabilities for monitoring Amazon Web Services (AWS). You can now monitor Amazon Elastic Kubernetes Services (EKS) containers from New Relic One when you use AWS Fargate as a serverless deployment platform.
Serverless computing has gained importance over the past few years because of advantages for software engineering teams:
- Fewer costs: You pay only for your use, instead of paying by server unit.
- No need to maintain servers: Serverless computing eliminates installation and maintenance tasks.
- Decreased time to market: Developers and architects can run, test, and deploy their code without relying on operations teams.
- Productivity: Developers can focus on what matters—creating better software, not installing and maintaining servers.
Our new integration injects a sidecar container in the Fargate node so that New Relic receives information from kube-state-metrics, kubelet, and cAdvisor to achieve full observability of the Kubernetes cluster.
Our ESK Fargate integration supports any Fargate setup, whether the cluster is only composed of Fargate nodes or if it also coexists with EC2 nodes. Depending on the node, the container will be injected on the same pod (Fargate node) or deployed in an exclusive pod (EC2 node).
The EKS Fargate integration is compatible with the New Relic One Kubernetes cluster explorer, providing a holistic view of a Kubernetes cluster.
You can easily filter Fargate nodes by using
The Kubernetes dashboard has been improved to list Fargate nodes. It distinguishes standard nodes from Fargate serverless nodes, as shown in the following example:
To learn more about this new AWS integration, and to see how easy it is to get started collecting, processing, exploring, visualizing, and alerting on your Amazon EKS on AWS Fargate environment, check out our EKS Fargate documentation.