Amazon Elastic Container Service for Kubernetes, or Amazon EKS, is a hosted Kubernetes platform that is managed by AWS. Put another way, EKS is Kubernetes-as-a-service, with AWS hosting and managing the infrastructure needed to make your cluster highly available across multiple availability zones. EKS is distinct from Amazon Elastic Container Service (ECS), which is Amazon’s proprietary container orchestration service for running and managing Docker containers.

Working in C#, as with any language, you’ll soon find that that you need to do some debugging. With C#, thankfully, due to a plethora of debugging tools and techniques, troubleshooting is usually straightforward.

In Part 1 of this series, we looked at key metrics for tracking the performance and health of your EKS cluster. Recall that these EKS metrics fall into three general categories: Kubernetes cluster state metrics, resource metrics (at the node and container level), and AWS service metrics. In this post, we will go over methods for accessing these categories of metrics, broken down by where they are generated.

In this post, we’ll explore how Datadog’s integrations with Kubernetes, Docker, and AWS will let you track the full range of EKS metrics, as well as logs and performance data from your cluster and applications. Datadog gives you comprehensive coverage of your dynamic infrastructure and applications with features like Autodiscovery to track services across containers; sophisticated graphing and alerting options; and full support for AWS services.

We are really happy to announce that we have released a plugin which allows to take captures using Sysdig in your Kubernetes cluster with just one simple command. And the answer for the next question you are asking yourself, is no. You don’t need to have Sysdig preinstalled in your cluster for this to work! This is our contribution to help you with your Kubernetes troubleshooting efforts.

There is a lot of industry buzz around how AIOps will affect change within IT Operations (ITOps). According to Gartner, Inc., the term “AIOps” describes platforms that combine big data and machine learning to support ITOps. This means that the problems being solved aren’t novel, the approach is. In ITOps or any other business unit, there are two primary constraints: time and money.

The primary intended use, in the case of Healthchecks.io, is to monitor the regularly running tasks on servers, such as cron jobs. However, the “alert me if X doesn’t happen on time” functionality can be useful in many other contexts too. One of the quirkier ways I’ve been personally using Healthchecks.io is to help my progress towards the Sojourner medal in Ingress.

Kubernetes is an open-source orchestration platform for working with containers. At its core, it gives us the means to do deployments, easy ways to scale, and monitoring. In this article, we will talk about the built-in monitoring capabilities of Kubernetes and include some demos for better understanding.

Imagine, you dear reader, have an e-commerce website (it’s 2019, after all) where you sell artisanal hot dogs. This site is built on several services that talk to each other to make sure your customers can easily purchase their organic, grass-fed hot dogs.

In this article, we offer you the possibility to make an approach to the issue of Citrix NetScaler monitoring, based on the scope of this product line and the visibility challenges involved, to finally propose the solution provided by Pandora FMS in this regard.