Skip to content

Document the Traffic tab and traffic history (DEPLOY-200) - #1358

Open
peter-vapi wants to merge 3 commits into
mainfrom
peter/DEPLOY-200
Open

peter-vapi wants to merge 3 commits into
mainfrom
peter/DEPLOY-200

Conversation

@peter-vapi

@peter-vapi peter-vapi commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Description

Documents the assistant Traffic tab, its per-version metrics, and the traffic history panel. All three rolled out to every org that has traffic splitting on 2026-10-23. Requested by Bets after the rollout; text only, no screenshots. Linear: DEPLOY-200 (follow-up to DEPLOY-183).

  • New fern/assistants/versioning/traffic-tab.mdx, titled "Compare versions on the Traffic tab". It explains what each view answers, how to open the tab (Dashboard and API tabs), the range menu including the five previous splits, focusing on versions, how to read each card (p50/p95, cost and latency parts, ended reasons), and a worked canary-ramp example.

  • New fern/assistants/versioning/traffic-history.mdx, titled "Review traffic history". It explains opening the panel from More actions, reading an entry, opening a split's metrics on the Traffic tab, Edit split, and the list API.

  • traffic-splitting.mdx links to both pages, renames "the traffic pill" to the Traffic header entry, and points "Comparing versions fairly" at the tab.

  • docs.yml: "Traffic splitting" changes from a page to a section that keeps the same path, now without the beta badge, with "Compare versions" and "Traffic history" nested under it.

  • openapi-overrides.yml: the five /traffic-allocations endpoints are overridden to generally-available, since the vapi controller still stamps them beta.

No merge dependency. Per Bets's review, the empty-state paragraph (which described the unmerged VapiAI/vapi#23891) is removed, along with the org-enablement prerequisite; the permissions bullet now names the built-in roles. Everything describes behavior already on main, written so it holds whether or not David's PAL-1190 polish (#24139–#24141) lands.

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work
  • Check that the nav shows "Traffic splitting" as a section with both new pages under it
  • Check that the three API reference links (metrics, list, latest) resolve

- New traffic-tab.mdx documents the assistant Traffic tab: per-version
  volume, configured vs actual share, duration, cost per minute,
  latency, and ended reasons, plus the metrics API and a worked
  canary-ramp example
- New traffic-history.mdx documents the traffic history panel: every
  split change with its shares, note, author, and timestamp, plus the
  List traffic allocations API
- Cross-link both new pages from traffic-splitting.mdx so readers can
  jump from editing a split to reviewing its performance or history
- Promote "Traffic splitting" from a page to a section in docs.yml nav,
  nesting "Compare versions" and "Traffic history" underneath it

Fixes DEPLOY-200

OpenCode session ID: ses_e961a8a91ffeceqON7606jgiGn
@github-actions

Copy link
Copy Markdown
Contributor

- Replace the org-enablement and split-read-permission bullet with a
  direct statement naming the built-in Admin, Editor, and Viewer
  roles that can open the tab, falling back to permission language
  only for custom roles
- Remove the paragraphs describing the empty-state messaging and
  the URL-persisted range/version selection, since bets review
  flagged them as unnecessary detail for this section

OpenCode session ID: ses_e961a8a91ffeceqON7606jgiGn
@github-actions

Copy link
Copy Markdown
Contributor

Traffic splitting left beta on 2026-10-23 (DEPLOY-200), but the
vapi controller still stamps these endpoints beta by default.

- Override x-fern-availability to generally-available for all five
  /traffic-allocations endpoints (list/create, latest, metrics, get by id)
- Drop the beta availability flag from the Traffic splitting nav
  section in docs.yml so the sidebar badge matches the API reference

OpenCode session ID: ses_e961a8a91ffeceqON7606jgiGn
@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant