Tags give the ability to mark specific points in history as being important
-
collector-v3.10.0
815981a2 · ·Release collector v3.10.0 - GraphQL 100% database coverage + modular refactor Features: - 100% database coverage (73 new fields) - 4 new reference table queries - Refactored into 20 modular files - Improved maintainability - No breaking changes
-
-
schema-v3.9.2
5a188bcd · ·Schema v3.9.2 - Normalized alert_history (removed redundant severity column)
-
schema-v3.9.1
b37f06b4 · ·Schema v3.9.1 - Remove deprecated metrics_network_ip, restore reference tables with foreign keys
-
collector-v3.9.0
59ed7f2a · ·Release collector v3.9.0 - GraphQL Complete Coverage Features: - Complete GraphQL API coverage (100%) - DLQ management (queries, stats, retry, cleanup) - System metrics (uptime, load, processes, file descriptors) - GPU metrics (AMD/NVIDIA/Intel with per-process tracking) - Network state (interface state, IP changes, IP metrics) - Horizontal scaling (orphaned probes, collector assignment) - Metric labels (custom tagging and filtering) Coverage: - Database tables: 18/18 (100%) - REST endpoints: 19/19 (100%) - Queries: 21 (+11 new) - Mutations: 14 (+2 new) - Code: +1,219 lines Performance: - Continuous aggregate support (raw/5m/1h/1d) - 10x faster for 30+ day ranges - 50x faster for 6+ month ranges Documentation: - TASK-LIST.md with complete task breakdown - GRAPHQL-COMPLETE.md with examples - Updated GraphQL playground
-
schema-v3.9.0
344a20ae · ·Database Schema v3.9.0 - Reference Tables with Foreign Key Constraints New Features: - alert_severities reference table (info, warning, critical) - metric_types reference table (system, cpu, memory, disk, network, temperature, gpu) - Foreign key constraints on alert_rules table - Helper functions: get_valid_severities(), get_enabled_metric_types() - UI metadata (colors, emojis, display order) Benefits: - Prevents invalid severity/metric_type values - Type safety via database constraints - UI metadata stored in database - Easy expansion without schema changes Compatibility: - Non-breaking upgrade from v3.8.0 - Compatible with Collector v3.8.0+ - Migration file: 11_v3.9_reference_tables.sql Files: - Complete schema: schema-v3.9.0.sql (105 KB, 2523 lines) - SHA256: 08e063a06f7663c8caa15f445197e0d5bca2792fe2248e65665a36cdfb8ab064
-
collector-v3.8.8
a9886e6d · ·Collector v3.8.8 - System metrics collection and request_system config support Complete fix for system metrics: 1. Added "system" to scraper default metric types 2. Added request_system configuration option (was missing) 3. Added RequestSystem field to GRPCConfig struct 4. Added system handling in ToMetricTypes() function 5. Added System metrics checkbox to bootstrap wizard Configuration: [grpc] request_system = true # Now properly supported Impact: - System metrics now populate metrics_system table - request_system config option now works correctly - Full observability of system-level health metrics - No configuration changes required for default behavior
-
-
collector-v3.8.2
baa46510 · ·Collector v3.8.2 - Alerting Bootstrap Implementation Implemented missing bootstrap functionality for loading default alert rules and channels from configuration file into database. New Features: - Bootstrap default_rules and default_channels from config on startup - Automatic rule-to-channel binding - Idempotent operations (ON CONFLICT DO UPDATE) Bug Fixes: - Fixed database schema example rules (incorrect field names) - Fixed documentation: channels (not channel_ids) Files: - internal/alerting/bootstrap.go (NEW) - Updated: collector.go, CHANGELOG.md, ROADMAP.md - Fixed: schema example rules in 10_v3.8_schema.sql
-