Website Observability Platform
An internal Next.js dashboard unifying monitoring of Oxford's web estate, property pages, Netlify sites, Agility CMS, GitHub repos, SEO/OG tags, and GTM trackers, replacing manual checks across disconnected tools.
Overview
- Project Type: Internal observability and monitoring platform
- Platform: Next.js, hosted on Netlify
- Team: Neal Miran (Lead)
- Status: Active, in production
Oxford's web estate had grown into a collection of disconnected surfaces: property pages, Netlify-hosted sites, Agility CMS content, GitHub repositories, SEO and Open Graph tags, and Google Tag Manager trackers. Checking the health of any one of them meant logging into a separate tool, and there was no single place to see the whole picture at once.
The Website Observability platform pulls all of it into one internal dashboard, built on Next.js and hosted on Netlify alongside the sites it monitors.
Key Features
- Unified Monitoring: A single dashboard surfaces the health of property pages, Netlify deploys, Agility CMS content, and GitHub repositories, replacing manual checks across disconnected tools.
- Multi-API Integration: Pulls live data from Oxford's leasing API alongside the GitHub, Google Tag Manager, and Netlify APIs, rather than polling each system by hand.
- SEO and Tag Visibility: Tracks SEO and Open Graph tags and GTM tracker status across the site, surfacing issues before they reach production or get noticed by search engines.
- Built for the Team: Used daily by the DevOps and SRE team to catch deploy issues, broken integrations, and missing metadata without switching between five different tools.
Technologies Used
Powers the dashboard itself, server-rendering live data pulled from four different APIs on each request.
Hosts the platform, and its API is one of the four data sources the dashboard polls to check deploy status across Oxford's other Netlify-hosted sites.
Repository and deploy status across Oxford's web codebases, surfaced directly in the dashboard via the GitHub API.
Tracker and tag status across the web estate, checked via the GTM API rather than manually auditing each site.
Outcome
What used to require checking five separate tools now lives in one place. The platform has become a standard part of the team's workflow for catching deploy issues, broken integrations, and missing metadata early, and it was built as a natural extension of the observability and reliability work that comes with owning Oxford's digital products end to end.