Say which AI observability route the homepage screens come from - #933
Merged
Merged
Conversation
The AI card offered two routes, Via AI Sessionizer and Via Gateway, but every screen in it is AI Sessionizer with Claude Code. A gateway watches model and MCP calls as traffic instead. The card copy now says what each route gives, the note under the screens names the one they come from, and the gateway link says it is traffic. The section below leads with the same distinction, and its heading names the workflow as AI Sessionizer's. The copy also claimed estimated cost. The gateway dashboards report requests, latency, tokens and streaming timings by provider and model, and AI Sessionizer never estimates cost, so the claim is replaced with token rates and that breakdown.
✅ Deploy Preview for skywalking-website-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
The AI card in the hero offers two routes, Via AI Sessionizer and Via Gateway, as equals. Every screen in the card is AI Sessionizer with Claude Code: the conversation replay, the change inspector and the token heatmap. A gateway watches model and MCP calls as traffic, and shows none of that.
The copy also claimed estimated cost, which neither route reports. The Agent Router dashboards cover requests, latency, tokens and streaming timings broken down by provider and model (dashboard docs), and the AI Sessionizer export page lists cost among the metrics it forwards but never estimates. The claim is replaced with token rates and that breakdown.
Text only, no layout or style changes. Checked with a local Hugo build at 1440px and 700px: the two hero cards stay aligned, and the footer links stay on one row at both widths.
A screenshot of an Agent Router dashboard would let the card show both routes, as a fourth tab beside Conversations, File changes and Token usage. The repository has none, so this change stays in the copy.