Skip to content

Fix poison wait false positives and alert log parsing (#445)#448

Merged
erikdarlingdata merged 1 commit intodevfrom
fix/poison-wait-false-positives-dev
Mar 6, 2026
Merged

Fix poison wait false positives and alert log parsing (#445)#448
erikdarlingdata merged 1 commit intodevfrom
fix/poison-wait-false-positives-dev

Conversation

@erikdarlingdata
Copy link
Copy Markdown
Owner

Summary

Cherry-pick of 564bab0 which was accidentally merged to main via PR #447 (should have targeted dev).

Test plan

  • Verify poison wait alerts only fire for recent activity
  • Verify alert history shows correct numeric values

🤖 Generated with Claude Code

Cherry-pick of 564bab0 (accidentally merged to main via PR #447).

The Lite poison wait query had no time filter, so stale data from days/weeks
ago with high avg waits kept triggering alerts indefinitely. Added a 10-minute
window matching Dashboard's existing filter.

Also fixed alert history logging: non-numeric display strings (poison wait,
LRQ, TempDB, job alerts) failed double.TryParse and logged as 0/0. Added
optional numeric parameters to TrySendAlertEmailAsync so call sites can pass
actual values for the DuckDB alert log while keeping display strings for emails.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@erikdarlingdata erikdarlingdata merged commit fa4dde4 into dev Mar 6, 2026
3 checks passed
@erikdarlingdata erikdarlingdata deleted the fix/poison-wait-false-positives-dev branch March 6, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant