Operations | Monitoring | ITSM | DevOps | Cloud

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.

Large applications can produce very large symbol files when debug information is enabled (especially at the higher, more verbose levels of debug info!). This article describes some techniques for reducing debug symbol file sizes! Like Interrupt? Subscribe to get our latest posts straight to your mailbox.

We at Catchpoint are always striving to help our customers improve their products’ user experience, because, as we believe that “the experience is the point.” With a motto like that, you can bet we take the usability and effectiveness of our own platform very seriously, and are constantly striving to deliver a world-class user experience in the Catchpoint Portal. With that in mind, we have spent the better part of the last few years redesigning Catchpoint Portal from the ground up.

At Lightspeed, we maintain multiple large iOS projects as well as their modularized dependencies. The last year of acquisitions brought together many different approaches to CI/CD at our company. I recently led the initiative to bring these projects and practices into alignment. In this post, I will explain the goals we had for our continuous integration pipeline and the implementations we used to achieve them.

Android Manifest file is essential for any Android app, which contains specific information about your app, Android build tools, Google Play, device permissions, app launch information, operating system config and more. Every Android app must have an AndroidManifest.xml file in the directory structure. Android Manifest usually contains pre-defined or static information which is then used to run the app.