Operations | Monitoring | ITSM | DevOps | Cloud

In this guide, I will deploy a Healthchecks instance on a VPS. Here’s the plan.

On the 2nd of May 2023, Jaspreet Kaur of the Azure Automation Product Group released this blog, providing an update on updates to Azure Automation in 2022 and what is in the pipeline for 2023. In the blog, Jaspreet detailed the major changes that Microsoft have made to the core of Azure Automation to improve the reliability and scalability of the underlying infrastructure.

Migrating data can be tricky and stressful, even under the best conditions. Jira migrations can be particularly complicated due to the various applications many organizations use in conjunction with it. As you are likely aware of, in an effort to focus on offering a better Cloud service, Jira Server has reached the last stage of its End-of-Life transition, with no further support planned after Feb. 2024.

We've seen a tremendous transition in the architecture of our systems over the years, from basic, linear systems to increasingly sophisticated, non-linear systems. We've moved away from monolithic programs, where a single person could comprehend the entire operation of a system, and toward a distributed world dominated by a microservices design.

Since we launched the new SquaredUp last Fall, our focus has been making it easier than it’s ever been to connect to any data source, build beautiful dashboards, and share them with anyone. Today we’re excited to announce a fully redesigned dashboarding experience that does just that. The new dashboarding experience remains backed by data mesh technology, which means your data stays where it lives – it’s simply stitched together and available on-tap from the source.

Enterprises are accumulating more and more observability and security data in isolated silos, not much different than the dust and spare change under couches and chairs in your grandparent’s rarely-used living room. There is something of value in both examples, but the nature of the value is very unclear and hard to measure without a lot of effort.

AWS users usually assume that Northern Virginia, also referred to as US East (N. Virginia) and us-east-1, is the least reliable in terms of uptime. We analyzed AWS outage history in 2022 across regions to see if N. Virginia, indeed, had the most downtime. Then we reviewed and proved some of the theories as to why N. Virginia has the most outages.

It’s a fact of life within the SaaS world that some features will perform better or worse than others in terms of costs versus revenue. If it were possible to develop every single new release in a way that it would flawlessly maintain desired profit margins, everyone would be doing it. What separates the major players from companies that struggle year after year is how they monitor and respond to changing circumstances as they arise, and whether they learn from past mistakes.

Today's applications are incredibly intricate and interconnected, often relying on numerous third-party services and libraries. With this complexity comes an increased likelihood of things going wrong. However, an error doesn't usually announce itself with great fanfare and a detailed explanation. More often than not, it shows up as an unexplained crash, a suspicious slowdown, or a surprising output. Error logging shines a spotlight on these problems.

At one particular time, a developer would spend a few months building a new feature. Then they’d go through the tedious soul-crushing effort of “integration.” That is, merging their changes into an upstream code repository, which had inevitably changed since they started their work. This task of Integration would often introduce bugs and, in some cases, might even be impossible or irrelevant, leading to months of lost work.