Easy Monitoring of Your Netlify Builds
Tags: jamstack, webdev
Published: 2019-11-07 19:07:20

---
title: Easy Monitoring of Your Netlify Builds
published: true
description: A new tool let's you automatically detect and monitor your Netlify builds from your own site.
cover_image: https://thepracticaldev.s3.amazonaws.com/i/s6o2q70jsu8b7jl2ksd8.png
tags: jamstack,webdev
---

The [JAMstack](https://jamstack.org/) architecture for building web apps has a ton of benefits from better speed, to better security, to better flexibility. And, let's be honest, the development experience overall is generally better as well (remember when you had to install a local application server, web server, database server and more?). Popular services like [Netlify](https://www.netlify.com/) make the whole experience better too by creating a continuous deployment experience that includes things like form handling, serverless functions and more.

But managing JAMstack sites isn't without its daily frustrations. For instance, when I check in a change or modify the content in the CMS, I am often left refreshing the page until I see the change live. That's not an optimal experience but it gets even worse when the change isn't obvious like a title or image, but instead is something behind the scenes in the HTML, CSS, JavaScript or serverless functions. I end up like...

![refresh, refresh, refresh](https://thepracticaldev.s3.amazonaws.com/i/422bls6cnkthq77fkhje.gif)

## Monitoring Netlify Builds with the Stackbit Control Center

This week [Stackbit](https://www.stackbit.com/) released a new feature that can improve this workflow (full disclosure: I am a developer advocate for Stackbit). The [Stackbit Control Center](https://www.stackbit.com/control-center/) actually sits on your web site and is visible only to you, not your users, while offering the following features.

1. Automatically detect and notifies you when a Netlify build is triggered - regardless of how it is triggered.
2. Monitor the progress of a Netlify build so that you know exactly when a change is live.
3. View the live build logs without ever leaving your page, so that you immediately know if there is a build error or delay.
4. Quick access to your projects associated services including such as the Netlify project dashboard and GitHub repository (or the associated CMS if the project was created using Stackbit).

![Stackbit control center feature overview](https://thepracticaldev.s3.amazonaws.com/i/s9pl2o06rao4ss9yvub5.gif)

Oh, and, by the way, it's free.

## Installing the Control Center?

This is usually the point where I'd be telling you that you need 1.5k different npm packages installed and to rewrite your site in React/Angular/Svelte for this to work. Good news - that's not the case. Here's how to add it to any existing site deployed to Netlify:

1. Go to [https://www.stackbit.com/control-center/]().
2. Click "Pick any Netlify Project".
3. Select which projects you would like to enable the control center on.
4. Enjoy!

But will this work on your site?

If your site is deployed to Netlify, yes it will! Whether it uses Gatsby, Jekyll, Hugo, VuePress, any other static site generator or, for that matter, no static site generator at all - it will work.

> Behind the scenes this uses Netlify's [Snippet Injection](https://docs.netlify.com/site-deploys/post-processing/snippet-injection/) and [APIs](https://docs.netlify.com/api/get-started/) to work. If you want to know more, check the [FAQ](https://www.stackbit.com/control-center/#faq).

## Go Forth and Deploy with Confidence!

![deploy!](https://thepracticaldev.s3.amazonaws.com/i/364j8tm49mfk3sg5pp9t.png)

Ok, maybe that's a bit over the top, but hopefully this tool can help make the whole experience of deploying JAMstack sites more transparent and save devs some time and frustration.