Fingerprint failed-job alerts (#1154 follow-up)#1157
Merged
Conversation
follow-up) BuildFailedJobContext (both apps) attached no #1140 incident, so two distinct failed jobs in the same window coalesced under the metric-key fallback of the #1154 per-fingerprint cooldown. Attach a Job fingerprint keyed by job name (scoped to the instance via serverName), mirroring the sibling BuildAnomalousJobContext. Both apps; serverName threaded to the builder. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
pull Bot
pushed a commit
to ehtick/PerformanceMonitor
that referenced
this pull request
Jun 29, 2026
…conciliation My first changelog pass walked only the most recent commits and missed a large middle band of post-3.0.0 work. Reconciled the full merge list (96 PRs since v3.0.0) against the changelog and added every previously-missing user-facing entry: - Advice engine: the sourced/fact-composed advice rebuild (erikdarlingdata#1244) + the correctness cluster (erikdarlingdata#1185 PLE, erikdarlingdata#1187 MAXDOP topology code-fix, erikdarlingdata#1192, erikdarlingdata#1194 five wrong claims, erikdarlingdata#1196-erikdarlingdata#1198/erikdarlingdata#1203 composer value-stating) - In-app plan navigation on every query surface (erikdarlingdata#1184) - Dashboard Queries/tab-load responsiveness (erikdarlingdata#1181/erikdarlingdata#1182/erikdarlingdata#1190) - Active Queries refresh-on-view (erikdarlingdata#1183); themed resolved/cleared toasts (erikdarlingdata#1186) - Desktop single-instance upgrade handoff (erikdarlingdata#1148) - Lite interactive UI-thread offload (erikdarlingdata#1193/erikdarlingdata#1202); View Plan no-op fixes (erikdarlingdata#1181/erikdarlingdata#1190) - FinOps Database Sizes init-order race (erikdarlingdata#1179) - Failed-job alert dedup + restart-replay (erikdarlingdata#1157/erikdarlingdata#1173) - Dashboard anomaly/baseline drift vs Lite (erikdarlingdata#1155) [3.1.0] is now 8 Added / 11 Changed / 17 Fixed; all 46 issue/PR refs link-resolve. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Follow-up to #1154 / #1156.
BuildFailedJobContext(both apps) attached no #1140 incident, so two distinct failed jobs arriving in the same window coalesced under the metric-key fallback of the new per-fingerprint cooldown — the second was suppressed. This attaches aJobfingerprint keyed by job name (scoped to the instance viaserverName), a direct mirror of the siblingBuildAnomalousJobContextwhich already does exactly this.serverNameis threaded into the builder; both apps updated identically.Build: both apps compile warning-clean (0/0). Admin-merged after local build verification (trivial mirror of shipped, tested code — no shared logic touched); the post-merge
devbuild runs the full suites as backstop.🤖 Generated with Claude Code