Add PQS Troubleshoot page and re-sync Configure/Operate to PQS 3.5 - #1395
Merged
Conversation
Convert the PQS troubleshoot index and its 750-line runbooks reference into a new page, placed after Optimize in the nav. While sourcing it found that Configure and Operate were pinned to PQS 3.4 even though Configure, Operate, Observe, and Recover all have real content changes in 3.5 (dynamic Daml package reload, pruning-state queries, a new /readyz endpoint, removed representative-package-ID section), so those two pages are re-synced to 3.5 as well. Also fixes several pages worth of dangling RST cross-references that never resolved to real links, and adds dashboard/trace screenshots that were referenced but never copied into the images directory. Signed-off-by: 8bitpal <elias@zerolimit.es>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
8bitpal
marked this pull request as ready for review
August 14, 2026 12:18
Configure/Operate were re-synced wholesale to PQS 3.5, silently dropping the PQS 3.4 behavior that MainNet/TestNet still run. Diffed the 3.4 and 3.5 sources and added <Tabs> only at the four points that genuinely differ (pruning-state query, representative package ID support, /readyz endpoint, dynamic Daml package reload), leaving the unchanged bulk of the page as a single verbatim block. Signed-off-by: 8bitpal <elias@zerolimit.es>
This was referenced Sep 1, 2026
The metrics-dashboard section carries panel names and screenshots from an earlier dashboard revision. Metric names (pipeline_*, watermark_ix) verified current against scribe 3.5.1 Grafana dashboards; adds a reader-facing note that panel titles in the shipped dashboard may differ. Signed-off-by: 8bitpal <elias@zerolimit.es>
Jatinp26
approved these changes
Sep 1, 2026
thibault-da
pushed a commit
that referenced
this pull request
Sep 2, 2026
…1395) * Add PQS Troubleshoot page and re-sync Configure/Operate to PQS 3.5 Convert the PQS troubleshoot index and its 750-line runbooks reference into a new page, placed after Optimize in the nav. While sourcing it found that Configure and Operate were pinned to PQS 3.4 even though Configure, Operate, Observe, and Recover all have real content changes in 3.5 (dynamic Daml package reload, pruning-state queries, a new /readyz endpoint, removed representative-package-ID section), so those two pages are re-synced to 3.5 as well. Also fixes several pages worth of dangling RST cross-references that never resolved to real links, and adds dashboard/trace screenshots that were referenced but never copied into the images directory. Signed-off-by: 8bitpal <elias@zerolimit.es> * Split PQS 3.4/3.5 divergences into version tabs on Operate Configure/Operate were re-synced wholesale to PQS 3.5, silently dropping the PQS 3.4 behavior that MainNet/TestNet still run. Diffed the 3.4 and 3.5 sources and added <Tabs> only at the four points that genuinely differ (pruning-state query, representative package ID support, /readyz endpoint, dynamic Daml package reload), leaving the unchanged bulk of the page as a single verbatim block. Signed-off-by: 8bitpal <elias@zerolimit.es> * Flag stale Grafana panel names on PQS Troubleshoot page The metrics-dashboard section carries panel names and screenshots from an earlier dashboard revision. Metric names (pipeline_*, watermark_ix) verified current against scribe 3.5.1 Grafana dashboards; adds a reader-facing note that panel titles in the shipped dashboard may differ. Signed-off-by: 8bitpal <elias@zerolimit.es> --------- Signed-off-by: 8bitpal <elias@zerolimit.es>
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.
Summary
sdks-tools/development-tools/pqs/troubleshoot.mdx), converted from the PQS troubleshoot index and its 750-line runbooks reference, placed in the nav after Optimize./readyzhealth endpoint, and removal of the "Representative package ID support" section. Re-synced both pages to 3.5.