docs(self-hosted): document cost_usd telemetry fields#30
Open
brunobuddy wants to merge 1 commit into
Open
Conversation
mnfst/manifest now ships two optional cost fields in the daily telemetry payload — cost_usd_total and cost_usd_by_provider — both rounded to cents and derived from agent_messages.cost_usd. Update the "What gets sent" table to fifteen rows, mark the new fields with a footnote explaining they're optional (older installs omit them) and that they're a rollup of token counts × pricing — no new data leaves the box. Clarify the schema_version row to call out the additive-vs-breaking rule.
4 tasks
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.
Summary
Pairs with mnfst/manifest#1888, which adds two optional cost fields to the daily telemetry payload. Update the self-hosted telemetry docs so the published "What gets sent" table matches what installs actually ship.
cost_usd_totalandcost_usd_by_providerwith concrete examples and the same plain-language purpose column as the other rows.schema_version, and clarify that no new data leaves the box — cost is a rollup of token counts × the in-process pricing table.schema_versionrow's purpose column to call out the additive-vs-breaking rule directly, since two new fields just landed without a version bump.Why
Without this change the public docs disagree with the actual on-wire shape as soon as mnfst/manifest#1888 ships. Operators reading the docs would think the payload tops out at thirteen fields and be surprised when their reverse-proxy or in-house telemetry sink sees cost fields.
Test plan
npx mintlify dev) and confirm the new rows + footnote display correctly<sup>†</sup>) render in Mintlify's MDX flavor