Applications are built and run by many people and made of many components: infrastructure, code pipelines and end users to name a few. Understanding the status of those components and teams is never straight forward. In this blog, we will be unpacking the problem faced by most organizations and taking a look at how SquaredUp can empower you and your organization with status visibility across different teams / components / services – all in one view.
Following our very informative recent virtual roundtable of supply chain executives facilitated by my colleague David Kane, I was anxious to take a turn in the moderator’s chair for our next executive roundtable, ‘How to Maximize ROI of Your Inventory in Today’s Uncertain World?’, this past August 11.
Automation is like running a marathon. It sounds like a great and noble pursuit until you actually go out and start pursuing it. At that point, it's easy to fail if you don't prepare yourself ahead of time for the challenges that are inherent to the process. Indeed, although automation can provide a number of awesome benefits, whether you actually reap those benefits depends on how easy it is to implement and manage automation tools. And, as many teams discover, doing these things may be harder than it often seems.
We created experimental Docker image which tries to ensure high availability of your web service by dynamically refreshing Cloudflare DNS with healthy endpoints.
World-class incident responders are a strategic asset in today’s world where the frequency and sophistication of cyber security attacks continue to increase every year, as do the associated financial damages: As such, more and more organizations are looking to grow their cyber incident response expertise, both with inhouse staff as well as by engaging with third-party experts.
We've all done it: "that'll be simple, I'll just write a quick script and..." In the case of calculating on-call pay, we really have done it before: our team have built the on-call pay scripts for several companies, and each attempt was a painful, error prone process. While we believe everyone on-call should be paid for their inconvenience, relying on someones side-project or back-of-napkin maths to calculate pay leads to mistakes, frustration, and wasted time.
