The radical shift towards DevOps and the continuous everything movement have changed how organizations develop and deploy software. As the consolidation and standardization of continuous integration and continuous delivery (CI/CD) processes and tools occur in the enterprise, a standardized DevOps model helps organizations deliver faster software functionality at a large scale.

In the first two articles in this series about using serverless on an open source platform, I described how to get started with serverless platforms and how to write functions in popular languages and build components using containers on Apache OpenWhisk.Here in the third article, I’ll walk you through enabling serverless in your Kubernetes environment.

Pandora FMS 737 release includes a brand new feature: automated software agent deployment from the console. In addition, the Discovery feature is still being developed, incorporating a new Cloud plugin for Azure. A new SLA reporting feature has also been added with Failover modules and other small enhancements.

At Honeycomb, we’ve often discussed the value of making software deployments early and often, and being able to understand your code as it runs in production. However, these principles aren’t specific to only your customer-facing software. Configuration-as-code, such as Terraform, is in fact code that needs to go through a release process as well. Lacking formal process around Terraform deployment means a de-facto process that generates reliability risk.

Debugging. It’s one of the most time-consuming ways of finding a bug. As a senior .NET developer, I can tell you that it’s best to avoid the necessity for debugging altogether by writing clean code that’s covered by automated tests. If you’re a senior developer yourself, you probably already know this. And if you’re a junior developer, now you know it too! However, the world isn’t binary.

We’ve changed Transaction steps and Multi-step API Monitoring steps to Transaction credits and Multi-step API Monitoring credits. In short: Steps are used to group your actions in your monitor definitions, and credits are used to buy Transaction or Multi-Step API monitors. Let’s explain that in more detail.

In the world of Software Engineering, observability seems to be the talk of the town. We discuss it at conferences, read about it in blogs or articles, and see it promised to us by vendor after vendor. But what is observability? What issues have recently evolved to make it such an integral concept? What strategies are engineers employing to ensure observability? And most importantly of all, why are engineers looking to achieve it?

If you’re not familiar with APIs, let’s run through a quick primer. API stands for application programming interface and refers to a set of tools and protocols that makes it possible to easily and efficiently access a software or hardware system from the outside.

Tools like Rollbar have changed the way development teams are recording and managing their exceptions. What used to be a very personal developer-by-developer activity can now be a team-wide tool for greater transparency, and increased application quality. But many still treat exception monitoring as a developer activity, and they are not leveraging its benefits across all environments, from development to stage and integration, to systems testing and production.

On July 16, 1969, the Apollo 11 space flight launched toward the moon carrying a crew of three. Several days later, on July 20, 1969, the United States successfully landed two humans on the moon. Neil Armstrong and Buzz Aldrin later relaunched from the moon’s surface to join Michael Collins and return to Earth, splashing down in the Pacific Ocean on July 24, 1969.