liveBook · Manning

Analytics and monitoring

As explained in Build AI-Enhanced Web Apps

The collection and analysis of incoming requests, visits, and usage patterns for a deployed application.

Analytics and monitoring keep a deployed application observable after release. They combine traffic measurement, log inspection, alerting, and firewall controls to reveal usage, performance, availability, and security problems. section 9.6.3

A practical monitoring setup can include:

  • Traffic monitoring with Vercel Analytics for real-time page views, unique visitors, and performance metrics; Google Analytics and Plausible provide broader alternatives. section 9.6.3
  • Log management through Vercel’s searchable logs, with New Relic or Datadog available for deeper application analysis. section 9.6.3
  • Alerting through services such as PagerDuty or Sentry, which can notify teams about critical problems when platform monitoring lacks alert delivery. section 9.6.3
  • Firewall rules that log, deny, challenge, bypass, or rate-limit traffic, configured from the Vercel project dashboard. section 9.6.3

How Build AI-Enhanced Web Apps covers it

How deep it goes
Defines four operational components and names configuration locations and provider alternatives, without implementation code.
Examples
Uses Vercel Analytics, Google Analytics, Plausible, Vercel Logs, New Relic, Datadog, PagerDuty, Sentry, and firewall rules.
What it assumes
Assumes a publicly deployed web application and introduces the operational tooling needed after release.
What you can do after
Operate/configure a Vercel deployment with traffic insights, searchable logs, external alerts, and customizable traffic controls.
How it connects
Connects web analytics with application logs, alerting, performance monitoring, availability, and web application firewalls.

This explainer was generated by Manning's knowledge graph from the text of Build AI-Enhanced Web Apps. The section links point to the parts of the book it draws on.