Skip to content

BetterDB Monitor v0.3.0

Choose a tag to compare

View all tags
@KIvanow KIvanow released this 29 Jan 14:11
· 322 commits to master since this release
v0.3.0
833f8b2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Per-Webhook Configuration

Each webhook can now have its own thresholds, delivery settings, and alert behavior. This enables tiered alerting where different notification channels trigger at different severity levels.

Example use case:

  • Slack webhook triggers at 75% memory usage for early warning
  • PagerDuty webhook triggers at 95% for critical alerts only

New Configuration Options

Option Description
thresholds.memoryCriticalPercent Custom memory alert threshold (default: 90)
thresholds.connectionCriticalPercent Custom connection alert threshold (default: 90)
deliveryConfig.timeoutMs Request timeout per webhook (default: 30000)
deliveryConfig.maxResponseBodyBytes Response body storage limit (default: 10000)
alertConfig.hysteresisFactor Recovery threshold multiplier (default: 0.9)

UI Improvements

  • New Advanced Configuration section in webhook form for power users

Fixes

  • Fixed DI injection tokens for proprietary webhook services
  • Fixed PostgreSQL retry query timestamp comparison
  • Handle duplicate anomaly events gracefully with upsert
  • Use Docker Compose v2 command syntax

Improvements

  • DLQ service now respects per-webhook maxRetries setting
  • Webhook Pro module marked as global for proper DI resolution

Full Changelog: v0.2.0...v0.3.0

Assets 2
Loading