Repository navigation
feat: guide monitor setup through baseline learning - #1275
Merged
Merged
Conversation
Deploying edgewatch with
|
| Latest commit: |
3980156
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ebb52734.edgewatch-cpd.pages.dev |
| Branch Preview URL: | https://feat-guided-monitor-setup.edgewatch-cpd.pages.dev |
crypt0rr
marked this pull request as ready for review
October 9, 2026 11:04
This was referenced Oct 9, 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.
New monitors now follow Targets → Coverage → Schedule and alerts → Review, then open a job page that explains the first scan and remaining baseline samples. Users can switch to advanced creation without losing their non-secret draft, choose full or partial coverage explicitly, and review the server's estimated probe work before saving.
POST /api/v1/jobs/previewshares creation policy, installed exclusions, pinned profile validation, routing and tenant permissions. It performs no scan, DNS lookup, write, notification or scheduling. Creation and execution revalidate current state. Administrators can create/test a notification destination inside setup; operators select existing destinations or continue without alerts. Credentials remain transient and write-only.Creation and scan start remain separate operations. An ambiguous create outcome blocks resubmission; scan retry uses the saved job. Job detail derives learning, stalled/resumable work, and valid empty baselines from persisted observations while preserving explicit baseline approval and incomplete-scan protections.
Closes #1267.
Closes #1268.
Closes #1269.
Closes #1270.
Refs #1266 and #1271; final tracking issues close after production guides and release verification. Based on the merged Go 1.27.2 security fix #1265 / #1273. Keep the persistent dependency dashboard #8 open.
Validation:
go test -race -timeout=25m -coverprofile=coverage.out ./...and vet pass. Local aggregate Go coverage is 88.2% across 15 production packages (CI 88.1%); changed executable-line coverage is 95.61%. Whole-release-range security checks pass: lint 0 issues, no reachable Go vulnerabilities, npm audit 0 vulnerabilities.ebb52734reviewed on desktop and 320px mobile for all five affected guides, canonical URLs, search and HTTP 404; preview remains noindex. Production deployment757fcec6at merge commit7d1a7b6is verified on the canonical domain, including all five guides, 320px layout, search, HTTP 404 and the Go 1.27.2 development minimum.Compatibility: no schema migration, new runtime configuration or scanner/Compose/release-pipeline change. Existing saved-job editing, profile revisions, API creation defaults and baseline decisions remain authoritative. Intended release: v0.32.0, using the unchanged immutable candidate and runtime smoke workflow.