Tags give the ability to mark specific points in history as being important
-
collector-v3.10.3
ce213dcd · ·release(collector): v3.10.3 - Critical GraphQL bug fixes Fixed 5 breaking issues causing ALL GraphQL queries to return empty results: - alert_history: Wrong column names - alert_rules: Non-existent channels column - metrics_gpu: device_id type mismatch (STRING vs INT) - metrics_gpu_processes: device_id type mismatch - metrics_system: boot_time type mismatch (TIMESTAMPTZ vs BIGINT) Complete database schema audit performed. All resolvers now match DB exactly.
-
collector-v3.10.2
a5c655c0 · ·release(collector): v3.10.2 - Temperature metrics column name fixes Bug fix release resolving temperature query errors caused by using a single query for three tables with different column structures. Split temperature resolver into table-specific queries (CPU/System/Disk). All temperature queries now correctly match their respective table schemas.
-
collector-v3.10.1
5a4ff3f1 · ·release(collector): v3.10.1 - GraphQL resolver column name fixes Bug fix release resolving production errors where GraphQL queries failed due to column name mismatches between resolvers and database schema. Fixed 17 column name errors across 5 metric resolvers (CPU, Disk, Network, GPU, GPU Processes). All GraphQL queries now correctly match database schema v3.9.3.
-
-
-
-
-
-
-
-
-
-
-
collector-v3.7.0
2f7cf192 · ·Collector v3.7.0 - Built-in Alerting System Features: - Built-in alerting engine with 4 notification channels - Support for all 7 metric types - Database-backed rules and channels - Alert history and statistics - REST API for management Release Binaries: - sysmon-collector.x64 (42MB) - Linux x86_64 - sysmon-collector.arm64 (40MB) - Linux ARM64 - SHA256 checksums included Database Migration Required: - Apply 08_v3.7_alerting_schema.sql before upgrading Documentation: - See ALERTING.md for complete guide
-
v3.6.1
9dbb6b71 · ·Release v3.6.1 - Static Probe Management Bug Fix / Enhancement: - Added full interactive static probe management to TUI wizard - Users can now add/remove/configure static probes during bootstrap - Probe addition dialog with all fields (ID, address, hostname, labels) - Real-time probe list display with formatted output - Remove Last and Clear All operations Technical Changes: - Complete CRUD interface for static probes (Page 8/13) - Nested dialogs for probe and label management - Form validation and dynamic list updates - 93 lines added to bootstrap_forms.go User Impact: - No longer need to edit config file after bootstrap for static probes - Production-ready static probe configuration in TUI - Better UX for multi-VLAN/multi-subnet environments Compatibility: - Backwards compatible with v3.6.0 - Same binary size (~40MB x64, ~39MB arm64)
-
v3.6.0
80a15ab5 · ·Release v3.6.0 - TUI Bootstrap Wizard New Features: - Modern ncurses-style TUI wizard for bootstrap configuration - 13-page interactive form wizard with comprehensive settings - Automatic terminal detection with fallback to linear mode - Real-time database connection testing - Automatic token/secret generation - Service installation prompt Technical Changes: - Added tview-based TUI implementation (634 lines) - Terminal capability detection (TTY, TERM, SSH_TTY) - New --ui flag (tui, linear, auto) - Updated dependencies: tview, tcell Compatibility: - Backwards compatible with v3.5.0 - Binary size increased to ~40MB (x64) due to TUI dependencies - Falls back to linear wizard in non-TTY environments
-
collector-v3.6.0
c60a7f45 · ·Release collector v3.6.0 - Enhanced bootstrap wizard with system setup
-
-
v3.4.0
Release: V3.4.0 - Stable91ab16fa · ·Release v3.4.0 - Network State Tables Network IP storage redesign with state-based tables. Key features: - State-based network IP storage (99.4% storage reduction) - Change detection and audit logging - 50x faster queries - Backwards compatible See CHANGELOG.md for full details.
-
v3.3.1
0de4cf6b · ·v3.3.1 - Temperature Metrics Collection Fix Patch release fixing critical bug where temperature metrics weren't being collected. Fixed: - Scraper now requests 'temperature' metric type in gRPC calls - Temperature data from probes v2.1.1+ now flows correctly to database - Temperature tables populate with CPU, system, and disk temperature data Dependencies: - Updated probe dependency to v2.1.1 (includes symlink handling fix) Verified: - CPU temperature metrics (AMD k10temp sensors) - System temperature metrics (NVMe, GPU, memory sensors) - All storage tests passing See CHANGELOG.md for full details.