Measure Frontend performance monitoring with SQL and check the results
To measure frontend performance monitoring with sql, choose one workflow and its owner. Define the events, test them with known inputs, and write a query that answers a specific question.
- 1
Choose when to log
Choose the product routes and supported performance metrics that matter.
- 2
Capture the outcome
Begin with frontend_vital_measured, frontend_navigation_completed, frontend_resource_failed and document the grain of each event.
- 3
Check the stored rows
Review samples and thresholds for each route before alerting on a release.
- 4
Make the decision
Which routes have the lowest share of passing samples?
Agent prompt
Paste this into your coding agent
Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.
Frontend performance monitoring with SQL setup prompt
Instrument frontend performance with Telemetry.
Use /skill.md and this Telemetry API key: YOUR_API_KEY
Add typed frontend_vital_measured events with route_template, release, metric_name, metric_value, metric_unit, threshold_version, passed, device_class, and environment.
Create SQL and a dashboard for sample count, LCP, INP, CLS, and passing-sample rate by route and release. Require a reviewed minimum sample count before comparing releases or enabling an alert.
Use route templates, bounded device classes, and versioned thresholds. Do not log raw URLs, query strings, DOM content, form values, cookies, auth tokens, or unrestricted user identifiers.Setup steps
- 1Choose the product routes and supported performance metrics that matter.
- 2Emit typed browser measurements with route, release, threshold version, and environment.
- 3Send synthetic passing and failing samples from a test release.
- 4Review samples and thresholds for each route before alerting on a release.
Events to capture
Questions you can answer
- Which routes have the lowest share of passing samples?
- Did the latest frontend release change LCP, INP, or CLS?
- Does performance drop across devices or only in one device class?
Example event schemas
Event schemas for this workflow
Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.
Use these queries in Telemetry
Learn about Alerts
Add a threshold and recipients to your reliability query to get alerts.
Related SQL recipes
More SQL recipes
Run the query using this workflow's event fields and check the example result. Save the result to a dashboard or set up an alert.
Compare Core Web Vitals by route and release
Which route and release has the weakest frontend performance?
Open recipeRank JavaScript errors by route and release
Which route and frontend release produces the broadest JavaScript error impact?
Open recipeMeasure SPA navigation latency by route
Which destination routes have the slowest client-side navigation?
Open recipeCalculate browser long-task rate by route
Which routes and releases spend the most time in browser long tasks?
Open recipeFind slow frontend resources by host
Which resource hosts and types are slowing or failing page loads?
Open recipeNext step
Create the API key your agent will use
The free plan is enough to run the prompt, send test events, and review the first dashboard.
Related pages