Inside SquaredUp: Our real-world approach to cloud platform releases

Why pipeline monitoring matters

As Tim puts it, pipeline monitoring becomes essential as your DevOps environment scales. He identifies four key drivers:

Build status visibility: Email notifications work fine when you have one or two pipelines, but as that number grows, "it becomes a real challenge to understand exactly what's going through the system at any point in time."

Troubleshooting and optimization: Pipelines constantly evolve - teams add stages, remove them, adjust configurations. "Monitoring your pipelines will really help you target which areas need improvement and how you should tackle it," Tim explains. Maybe the duration becomes very long, or stages become problematic. Without monitoring, teams are guessing where to focus their efforts.

Cost management: Cost is always a factor in IT. Understanding what pipelines consume and how to optimize them delivers real benefits to both engineering teams and the business bottom line.

Deployment coordination: This is especially crucial for applications made up of multiple microservices or component parts built by different teams. As Tim explains, “You can have multiple pipelines doing multiple deployments, maybe to many environments, and all of that together is going to be what makes up one release of your product.” Understanding exactly what’s stuck, lagging behind, or successfully deployed matters not just for DevOps practice, but for hitting business goals.

Where Azure DevOps falls short

Azure DevOps provides some basic dashboards with pipeline views, but Tim’s team kept hitting critical limitations:

Limited widgets and visualization: You only get one visualization type per widget with very few parameters to scope the data. The options feel restrictive.

Limited configuration: There's minimal flexibility in displaying or manipulating data. The team needed more control.

Data scattered everywhere: This is the real pain point. It's hard to pull all the information together - within Azure DevOps itself, there isn't a comprehensive way to do this. Teams often resort to running automation to scrape data, export it, and inevitably end up in Excel.

Project-based constraints: This was the biggest headache. You can only create widgets for one project at a time. Since using different projects for different teams or applications is standard practice in Azure DevOps, this means creating multiple dashboards and constantly jumping between them.

How SquaredUp tackles these challenges

Tim highlights what makes SquaredUp different:

Connect to anything: SquaredUp integrates with Azure DevOps, GitHub, Jira, and virtually any data source. "One of the things we pride ourselves on is being highly configurable and being able to bring data in from pretty much anywhere," Tim says. Dashboards offer flexible visualizations with full control over tiles, layouts, and sizing.

See it your way: The platform uses color options and various formats - tables, charts, status indicators - to draw your eye to what's most important.

Break project boundaries: Unlike Azure DevOps, teams can combine data from multiple projects into one dashboard for a complete view.

Stream, don't store: SquaredUp uses a data mesh architecture that connects to data sources and streams information live, rather than having to build a large data warehouse and all of the challenges that come with that.

Dashboard walkthrough

Tim demonstrates the Cloud Platform Release dashboard, which provides at-a-glance visibility into the entire release pipeline - designed to present information in a way that's very accessible and you don't need to be scrolling through many pages of data.

The dashboard shows:

Release Queue & Status

• Current number of releases queued up
• Release status (Deploying, Paused/Unpaused)
• Releases awaiting production deployment with GA timings

Release Outcomes

• Releases successfully gone live (GA) - shown in green
• Failed releases - flagged in red for immediate attention
• Internal releases (RC) - filtered for internal tenants only
• Cancelled releases - tracked separately in orange

Pull Request Activity

• Closed PRs with details on ID, state, draft status, and assignee
• Open PRs currently in progress
  

The dashboard surfaces the key questions that matter in any release flow: How many releases are queued? What's currently deploying? Are there any failures blocking progress? Which PRs are ready to merge?

Making release flow visible

As Tim demonstrates throughout the video, monitoring pipelines shouldn't require jumping between tools, exporting to spreadsheets, or missing critical failures because information is scattered across multiple dashboards. The Cloud Platform Release dashboard shows how bringing everything into one configurable view transforms pipeline data into actionable insights.

Dashboards become even more powerful with SquaredUp's monitoring and notification capabilities. Teams can set up alerts via email, Slack, Teams, or any webhook-enabled service. They can even schedule dashboard deliveries - useful for quarterly planning sessions or regular reviews. And with the share functionality, anyone can access a read-only version of a dashboard without needing a SquaredUp license, making it easier to get buy-in across the organization.

Want to try it yourself?
Sign in to SquaredUp and start building your own release dashboard in minutes.