Repository navigation
Retire classic Prism assets and migrate saved SQL and builder alerts - #55
Merged
Merged
Conversation
Builder alerts were read-only in the native UI. The server already stores
and evaluates their generated SQL in `query` (the same path as code
alerts), and PUT /alerts/{id} accepts queryType "code" while keeping
state, mute and created time.
The detail page now offers "Convert to SQL rule", which opens the edit
form with the stored SQL shown exactly and every existing setting
(threshold, operator, window, frequency, severity, tags, targets,
opaque extra fields) prefilled. Opening the form only reads the alert;
nothing changes until "Convert and save". Cancel or a failed save leaves
the stored builder rule unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
List SQL /filters records (classic Prism queries with stream_name "sql" and SQL Logs views) in a read-only "Server saved queries" section of the SQL editor. Opening one creates an unsaved draft; copying one adds an independent browser-library entry, preserving existing local queries. Classic Logs views without a native explorer state can open their stored SQL in the SQL editor. Builder and search views are never translated and no server record is written, converted or deleted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 21, 2026
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.
Description
Source builds now embed only the native frontend. The classic Prism ZIP pin/download, compiled-asset overlays, fallback mount and comparison links are removed. Backend Prism APIs, node mode and stored documents remain supported.
The migration closes the main native editing/access gaps:
Deployment changes: build
frontend/and setNEXT_ASSETS_PATH. RemoveP_UI_ROOT=classicandLOCAL_ASSETS_PATH; both are rejected. Old/nextbookmarks redirect to root. Backend-onlyP_BUILD_NO_UI=1is restricted to debug builds. Releasebuild.zipremains the native frontend artifact.See the migration guide for remaining limitations: non-SQL classic builder/search views need manual recreation; server-library writes/sync, advanced dataset settings, metrics builder/catalog/histograms, Logs grouping and dashboard templates remain follow-ups. This PR does not include the separate dashboard persistence work.
Validation
/tmpquota. All affected checks passed in a five-test isolated rerun with disk-backedTMPDIR, zero retries and no console errors.cargo check --locked --testspassed with native assets and independently in backend-only debug mode. Focused routing/build-contract checks passed during implementation.Additional end-to-end validation uses Sol 6.1 and Opus 5.5 against
70568346:cargo build --locked -j 4linked successfully; the disposable backend reportsuiVersion: native-3.2.5.ERR_NETWORK_CHANGEDand passed alone. Saved SQL 10/10 and Logs-to-SQL 8/8 passed. No reproducible UI regression was established; this was not a clean uninterrupted full-suite run.Open backend validation finding: one repeated live migration run returned an empty result for the correct saved SQL/window around staging conversion. The server plan scanned zero files; a separate API probe caught a staging Parquet file-not-found 500 and transient stream-access 400s. The exact aggregate replay did not reproduce it in 361 requests. Query/staging/storage/sync code is unchanged from the PR base, but no baseline backend was run. The new tests remain strict, attach direct replay evidence on mismatch, and do not retry away failures. Details and artifact paths are recorded in
frontend/docs/validation-review.md.Not run: linked Rust tests, Docker image builds, cross-browser checks or real-IdP OIDC interoperability.
Need help on this PR? Tag
@codesmith-botwith what you need.