github caglaryalcin/OmniSight v2.4.2

latest releases: v2.7.10, v2.7.9, v2.7.8...
3 months ago

OmniSight v2.4.2 focuses on alert delivery reliability, predictable demo resets, current Proxmox Community Scripts compatibility, and dashboard polish.

Alert Reliability

  • Fixed recovered hosts and devices retaining an old DOWN cooldown, which could suppress a new outage notification for up to one hour.
  • Prevented repeated hourly DOWN notifications while the same incident remains active.
  • Failed notification deliveries now release the incident state so delivery can be retried.
  • Recovery and subsequent outage transitions now generate independent notifications.

Demo Environment

  • Demo settings, topology edits, removed demo agents, filters, card ordering, sidebar preferences, and other browser UI state now reset automatically each day.
  • Daily resets use Europe/Istanbul by default and can be changed with OMNISIGHT_DEMO_RESET_TIMEZONE.
  • Login sessions are preserved during daily resets.
  • Open demo pages detect a new reset day and reload into the default state.

Proxmox LXC and Community Scripts

  • Updated the LXC installer integration for the current community-scripts/core architecture and ProxmoxVED metadata format.
  • The standalone Proxmox wrapper now delegates to the canonical OmniSight CT script instead of patching framework source at runtime.
  • Community Scripts core now manages the container update command.
  • Update backups are restored before production dependencies are installed.
  • CI now validates the Community Scripts CT and install shell scripts.

Dashboard and Interface

  • Added thinner, theme-matched Firefox scrollbars to the sidebar and Recent Logs panel.
  • Preserved the Recent Logs DOM node and scroll position during dashboard refreshes, eliminating visible scrollbar jumps.

Validation

  • Expanded alert transition, demo daily reset, browser-state, LXC integration, and scroll-preservation smoke coverage.
  • Production dependency audit reports zero vulnerabilities.

Upgrade Notes

  • Existing OmniSight configurations and persistent data remain backward compatible.
  • No additional migration steps are required.

Don't miss a new OmniSight release

NewReleases is sending notifications on new releases.