Often there’s a focus on how a service is running from the perspective of the organization. But what does service health monitoring look like from the perspective of a user? There are many metrics that indicate the overall health of a container, vm, or application, but independently they do not indicate if the system is functioning correctly. Often these metrics (CPU, disk, memory) are too narrow, and they can be poor indicators. High CPU may be desirable or bursts of memory usage may be normal.

This is the third of a series of three articles focusing on Kubernetes security: the outside attack, the inside attack, and dealing with resource consumption or noisy neighbors. A concern for many administrators setting up a multi-tenant Kubernetes cluster is how to prevent a co-tenant from becoming a “noisy neighbor,” one who monopolizes CPU, memory, storage and other resources.

Orquesta is the new workflow engine in StackStorm. If you are on the fence choosing which workflow services to use from AWS, Azure, or GCP and you are thinking that this post is too long to read, then just skip ahead and run StackStorm.

How much infrastructure for a domain or application can fail before the customer starts to notice? What about before your productivity is affected? The answer to these questions will help you fully utilize uptime monitoring. Here are just a few examples of services that can be monitored for better piece of mind.

In health care, doctors know the average man or average woman is in fact, mythical. Everyone has their own unique problems, capabilities and life stories. DNA can be altered by the environment. Even identical twins will have different health histories and different propensities to contract and avoid certain illnesses. Each individual is different. The same can be said of IT — no two shops are ever exactly alike.

Errors are expensive; they steal resources allocated for other things and potentially negatively impact revenue and user sentiment. And, for teams comprised of volunteers working in their spare time, errors can take weeks to triage and resolve. So, despite what Google might tell you, Sentry for Good is not merely a solution to your pet’s pesky pheromone problems (although it is clearly also that, if PetSmart’s Google results are any indication).

This is the second edition of our features review from the past few years, here we will share some features that were created or updated in 2017. We are currently moving content from our old blog platform so all features mentioned here are not new but it is always good to take a fresh look at things. And as we are always upgrading & enhancing features, some of the items have been edited to reflect the current state.

Over the last year, along with Kubernetes, Serverless computing platforms have acquired tremendous mindshare among the development community. As Serverless implementations begin to proliferate, I want to make the case that there are tremendous synergies to be gained by bringing both these paradigms together. Some of these benefits have been covered in previous posts. The majority of enterprises are embarking on their DevOps journey. Scaling such processes across a large enterprise is complicated.

A while back, I wrote about how you can shave latency off every AWS SDK operation by enabling HTTP keep-alive, like this. It had the desired effect and I saw lots of people apply this technique in their projects. But it also resulted in the same 10 lines of code being copied and pasted everywhere! I began thinking about ways to distribute an optimized version of AWS SDK so everyone can benefit.

This month, we are excited to announce a new set of product capabilities and enhancements designed to ensure that teams can work in real time, all the time, wherever they are. Whether they’re on-the-go with their mobile devices or at their desks on a typical work day, we will continue to innovate without sacrificing ease-of-use and adoption.