Although there are many great tools out there to get on top of application monitoring, there’s one vital metric that’s often overlooked by us technical folks – cost. In the days of running apps on servers in private datacenters, the kit was a one-time purchase that the systems team had to deal with. But running apps in public clouds is a different story. Whether you’re running on VMs, containers in Kubernetes, or entirely serverless, execution of your code adds to the bill.

It's not like it used to be back in the day! Before CI/CD, we were building on-premises, service-oriented products following system style architecture and we were able to map out the build system and end-to-end process in a PowerPoint or Visio document. Although time-consuming and inefficient, it was relatively straightforward and the build pipeline was unlikely to change drastically. But that's no longer the case.

Project managing global software projects is always a challenge, contending with multiple time zones, tools, and teams. In these environments, the day-to-day life of a Project Manager is filled with status collections, project reporting, and little time for much else. While the detail will always matter – like team bug data, feature status, and build progress – there is a better way than collecting and reporting on all this data manually. Does this scenario sound familiar?

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.

I figure you’re doing okay with SquaredUp. It still works for you. Maybe you feel there are a couple of things that could be improved, but it’s not a big deal. So you’ve not upgraded yet. And frankly, because it all works fine and is still doing its job, you haven’t kept up to date on all the latest features rolled out in the SquaredUp updates. But…you’re missing out – on a lot.

SCOM has incredible powers, but it’s not always easy to find the root cause of issues fast. And you definitely don’t get one-click SCOM root cause analysis. We’ve all been there. A business-critical server goes down and you don’t know why. Let’s imagine you had a dashboard showing the health statuses of all your server groups and you notice that the United States is showing as critical.

We’re excited to announce that we’ve just released SquaredUp Dashboard Server 5.6! This Dashboard Server release covers multiple features that have been highly requested by the community. Prioritizing this user feedback, we’ve added some exciting new visualizations, features and enhancements. Read on to learn about the latest updates, or catch the full webinar recording at the bottom of the blog for a detailed demo by Senior Solutions Engineer Ashley Thompson.

Looking to keep an eye on logs and metrics from AWS or CloudWatch? There are several reasons you might want to build a CloudWatch dashboard somewhere outside of the CloudWatch console: Whatever the reason, we’ve put together a write-up to help you plug into CloudWatch to surface any logs or metrics in one place, for easy alerting and sharing, using the SquaredUp observability portal. You can get your own SquaredUp account, just head over to squaredup.io/get-started to sign-up for a free account.

We frequently get asked questions about how to maintain and optimize SCOM. So here are the top SCOM questions we get asked and answers from the experts.

We’ve just released SquaredUp 5.5! As always, you’ll find some great new additional features as well as enhancements in the SquaredUp Community, Azure, and SCOM Editions. Plus, the new 5.5 release works with SCOM 2022. Here’s a quick overview of what’s new: Check out the release webinar here or keep reading for all the juicy details.