Repository navigation
chore: Remove deprecated db.redis op - #19932
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The plan checks production client errors, sampled pageload count, and sampled navigation count. An issue escalates when hourly errors rise above the measured band. Services: PlanWhat changedThe Span Operations page no longer lists db.redis as a database span operation. A production deploy of develop-docs must finish before this change is live. The page path is /sdk/telemetry/traces/span-operations/. RiskA broken markdown table can fail the MDX build. A failed build blocks the whole site. A bad table after a successful deploy only breaks that page. Intended effectThis change only edits a documentation table. Sentry has no signal for the missing db.redis row.
Regression watchA render failure on this page can throw a client error. Page-level URLs are not separable, so watch site-wide errors. Traffic on sibling telemetry pages shares the same MDX renderer. A renderer throw would also show in these errors.
Not observablePage-level traffic is not separable. All pageloads use transaction Queries for Hourly pageload p95 ranged from 2.1s to 28.8s. That spread is too wide for a regression watch. Sentry cannot show whether the live HTML still contains the db.redis row. |
|
Verified in
|
No description provided.