Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes is a game-changer for enterprise organizations. Automating deployment, scaling, and management of containerized applications allows organizations to embrace a cloud-native paradigm at scale and more easily employ best practices, such as microservices and DevSecOps. But as with all tech, Kubernetes has its limits. Kelsey Hightower famously tweeted that “Kubernetes is a platform for building platforms. It’s a better place to start; not the endgame.”

Microservices are loosely coupled software that provides flexibility and scalability to a cloud environment. However, securing this open architecture from vulnerabilities and malicious actors can be challenging without a service mesh. This blog post will demonstrate how you can create an Istio and Calico integration to establish a service mesh that will manipulate HTTP traffic in the application layer.

As today’s enterprises shift to the cloud, Kubernetes has emerged as the de facto platform for running containerized microservices. And while Kubernetes operates as a single cluster, enterprises inevitably run their applications on a complex, often confusing, architecture of multiple clusters deployed to a hybrid of multiple cloud providers and private data centers. This approach creates a lot of problems. How do your services find each other? How do they communicate securely?

Development teams build modern applications using microservice architectures. Individual services are built and maintained by separate teams, and then these services are combined using container-based orchestrators to comprise a complete product offering. Microservices are a standard development method because they allow teams to iterate releases, providing ongoing new customer-facing features and bug fixes without needing to redeploy an entire platform or app.

In this previous article, we talked about how to monitor the Istio service mesh in Kubernetes with the out-of-the-box observability stack. This time, we will walk you through monitoring the Istio service mesh with Sysdig Monitor and how to troubleshoot issues. Istio service mesh provides special characteristics and functionalities for microservices running on Kubernetes.

The rise of the containerized software environment has left archaic, monolithic application structures behind. Cloud-native applications running via a range of containers, or individual, self-contained software packages, are now the norm. Platforms and tools like Kubernetes and Docker allow developers to create apps that work irrespective of device or operating systems, vastly reducing time to market and increasing potential user base numbers.

LM Envision is a unified observability platform from LogicMonitor that unites comprehensive monitoring and observability capabilities. In this blog post, we’ll show how to integrate Istio service mesh with a LogicMonitor APM so that application traces can be used within LM Envision to better understand, optimize, and troubleshoot application performance.