Add isolated Vercel Speed Insights drain receiver - #1
Draft
ausdisau wants to merge 1 commit into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds a separate
apps/observability-drainNode.js service for receiving Vercel Speed Insights Drain events outside the MapAble user-facing web request path.Receiver
GET /healthPOST /v1/vercel/speed-insightsx-vercel-signatureusing HMAC-SHA1 over the raw request bodyvercel.speed_insights.v1and known Core Web Vital metric typesPrivacy defaults
deviceId,city, andattributionpathby default/participant/[id]originMAPABLE_DRAIN_INCLUDE_PATH=trueOptional forwarding
DRAIN_FORWARD_URLcan send sanitized batches to an independent observability sink. Without it, accepted batches produce only structured aggregate runtime log entries.Why
A drain receiver improves MapAble's observability pipeline without putting telemetry ingestion on the production application's own API surface. This keeps monitoring failure domains separate and reduces the risk of participant-specific URL or device metadata being exported unnecessarily.
Vercel deployment contract
Create a dedicated Vercel project using:
ausdisau/MapAbleapps/observability-drainVERCEL_DRAIN_SECRETThen configure a Speed Insights Drain to send production events to:
https://<observability-project>.vercel.app/v1/vercel/speed-insightsDo not add Logs, Web Analytics, AI Gateway or Trace schemas until dedicated handlers and a privacy review are added.
Validation
Local Node test suite: 5/5 passing
Scope
This PR does not create or expose any participant-facing capability, modify the main web deployment, create a Vercel secret, enable a drain, or change production traffic.