Repository navigation
Let admins choose the trace backlog when enabling analysis - #1013
Draft
promptless[bot] wants to merge 10 commits into
Draft
promptless[bot] wants to merge 10 commits into
promptless[bot] wants to merge 10 commits into
Conversation
Adds a governance guide for the Promptless Dashboard's per-worker Trace analyzer control, previously undocumented, and the new backlog cutoff choice (All traces / Since date or time) from open source PR Promptless/promptless#5093.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ysis-backlog-cutoff # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ysis-backlog-cutoff # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ysis-backlog-cutoff # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
3 tasks done
…ysis-backlog-cutoff # Conflicts: # src/content/changelog/changelogs/september-2026.mdx # src/content/docs/docs/governance/deploy-the-worker/verify-your-deployment.mdx
Contributor
Author
|
I noticed that some CI checks failed for this PR. I'm investigating whether the failures are caused by this suggestion. If they're unrelated or pre-existing, I'll leave this suggestion unchanged and create a separate suggestion if a standalone docs fix is needed. |
… for the how-to template
This branch was successfully deployed
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.
Proposed changes
Documents a Promptless Dashboard admin control that had no prior coverage in this collection: an organization admin's per-worker-installation Trace analyzer toggle, and the new backlog-cutoff choice ("All traces" or "Since date or time") that opens on enabling/resuming, from open source PR Promptless/promptless#5093 ("Let admins choose the trace backlog when enabling analysis", @adit-chandra).
Adds a new guide,
docs/governance/deploy-the-worker/enable-trace-analysis.mdx, covering: enabling analysis and choosing the backlog; what "All traces" versus "Since date or time" means, including the activation floor and the model-provider data-exposure trade-off for "All traces"; pausing and resuming (and how that differs from the unrelated release-update pause on Manage updates and recovery); and recovering from a failed enable request. Adds disambiguating cross-links from Verify your deployment and Enroll your hosts, a reciprocal cross-link from Manage updates and recovery, a nav entry inastro.config.mjs, and a changelog entry.Open items to confirm once source PR #5093 merges (org policy: an open/unmerged source PR does not hold back research or authoring; this suggestion/PR stays in draft until then):
mainyet, this session had no reachable dashboard target, and no test scaffold exists yet for this governance/PIG dashboard surface (only the for-docs product dashboard has specs today). Follow-up: author.doc-detective/tests/enable-trace-analysis.spec.jsononce the feature is live and a login/fixture scaffold exists for this surface.manni metadata (after #1177): The new page carries a manni
id(governance-deploy-the-worker-enable-trace-analysis) andtype: how-to, pluslanguage,audiences, andlifecyclefrontmatter. It also has a matchingdocs.metadata.yamlentry and git-derivedcreated,last-updated, andownerstamps. These additions fix thevalidatecheck. The page also now hasOverviewandSee alsosections so it passesmanni lint structurefor the how-to template.Checklist