HitKeep 2.3.1: Clearer System Status For Backups, Workers, And Rejected Traffic
HitKeep 2.3.1 tightens the operational visibility added in 2.3.0. It is a small patch release for instance owners and cloud operators who rely on System Status to answer a simple question: is the instance healthy right now?
The release does not add a new analytics surface. It makes existing status data clearer for backups, worker connectivity, spam filtering, rejected ingest requests, and managed cloud operations.
What changed
Section titled “What changed”- Backup worker status: System Status now reports backup success, failures, recent failure count, last error, and next run time from the live backup worker.
- Worker health: leader instances now surface degraded NSQ worker connectivity instead of looking healthy when the producer is unavailable or failing.
- Spam and rejection counters: dropped spam hits, dropped spam events, rejected pageview ingest requests, rejected event ingest requests, and rejected AI fetch requests now increment system counters.
- Managed cloud status link: managed cloud admin settings now link directly to status.hitkeep.com for hosted incident status.
- Maintenance refreshes: the release also includes Go dependency updates and refreshed dashboard screenshots.
Upgrade guidance
Section titled “Upgrade guidance”All 2.3.0 operators should upgrade to 2.3.1. The update is especially useful for:
- managed cloud deployments
- instances using automatic S3 or filesystem backups
- high-traffic self-hosted instances where rejected or spam traffic should be visible
- clustered deployments where worker health needs to be explicit
Use the normal release artifacts from GitHub. There are no extra migration steps for this patch.