This document may contain technical inaccuracies, omissions and typographical errors, and Ampere is under no obligation to update or correct this information. In this white paper, we will demonstrate how to deploy an ELK stack on a Google Cloud Tau T2A GKE cluster to collect logs from pods inside a Kubernetes cluster.Īll data and information contained herein is for informational purposes only and Ampere reserves the right to change it without notice. The ELK stack gives developers the end-to-end ability to aggregate application and system logs, analyze those logs, and visualize insights for monitoring, troubleshooting, and analytics. Since 2015, the Beats family of lightweight data shippers has been an unofficial component of the ELK stack. Google Kubernetes Engine (GKE), which is a key infrastructure for containerized workloads, has supported the Tau T2A VMs since day one.Ī traditional ELK stack is comprised of Elasticsearch, Logstash, and Kibana. Google Cloud offers the cost-optimized Tau T2A VMs powered by Ampere Altra processors for scale-out Cloud Native workloads in multiple predetermined VM shapes – up to 48 vCPUS per VM, 4 GB of memory per vCPU, up to 32 Gbps networking bandwidth, and a wide range of network-attached storage options. This translates to industry leading performance/watt capabilities and a lower carbon footprint. The processors are also designed to deliver exceptional energy efficiency. This allows workloads to run in a predictable manner with minimal variance under increasing loads. They do so by using an innovative architectural design, operating at consistent frequencies, and using single-threaded cores that make applications more resistant to noisy neighbor issues. Ampere ® Altra ® processors are designed to deliver exceptional performance for Cloud Native applications such as NGINX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |