Operations | Monitoring | ITSM | DevOps | Cloud

Getting started with software can be confusing – depending on the complexity of the software, of course. Despite the extensive documentation available for Charmed Operator SDK and Juju some just prefer to watch video material to start with. So, let’s take the opportunity to have a look at available tutorials and presentations available on the Internet.

In part 1 of our synthetics series, we looked at tracking network performance to drive better business outcomes. Here in part 2 of our series, we’ll dig into the very first and most basic business outcome of using digital experience monitoring (DEM). That is, we’ll look at how to protect and grow revenue by proactively monitoring the health, availability and uptime of your critical applications and services, so you can fix issues before your customers’ experience suffers.

Business continuity is a crucial part of any scalable operations plan, but many businesses fail to realize how important it is until their first critical emergency. Only then does business continuity management come to the forefront of planning exercises, and stakeholders are forced to reflect on what went wrong, why it went wrong, and determine if they can avoid it happening again, or be better prepared if it does. The true business continuity management lifecycle begins long before an incident.

The global march towards delivering operational resilience across the financial sector steadily continues.

For most companies it’s difficult to organize cloud spend because it relies on manual effort, like tagging. At CloudZero, we’re dedicated to helping customers make sense of their cloud investment without manual and repetitive work. Our code-driven approach to cost allocation makes it easy for customers to organize spend even if they have poor tagging, shared resources, or containerized infrastructure. Quite simply, we organize cloud spend better than anyone else in the world.

In this k6 series I have covered HTTP request testing with k6 and performance testing with k6. I designed these tutorials to introduce you to k6 and to show you how to use k6 for performance testing of microservices. As the third tutorial in the k6 series, this will cover how you can store your k6 test results locally and also how to schedule your load tests using CircleCI’s scheduled pipelines feature.

In this article you will learn about Node-RED, a popular tool for rapidly gluing together different types of hardware and software. You’ll learn about some of the core concepts of Node-RED and then learn how to make some workflows like storing data from a sensor using an MQTT broker and InfluxDB.