Files
securityonion/salt
Mike Reeves d9a9029ce5 Adopt pg_partman + pg_cron for Telegraf metric tables
Every telegraf.* metric table is now a daily time-range partitioned
parent managed by pg_partman. Retention drops old partitions instead
of the row-by-row DELETE that so-telegraf-trim used to run nightly,
and dashboards will benefit from partition pruning at query time.

- Load pg_cron at server start via shared_preload_libraries and point
  cron.database_name at so_telegraf so job metadata lives alongside
  the metrics
- Telegraf create_templates override makes every new metric table a
  PARTITION BY RANGE (time) parent registered with partman.create_parent
  in one transaction (1 day interval, 3 premade)
- postgres_telegraf_group_role now also creates pg_partman and pg_cron
  extensions and schedules hourly partman.run_maintenance_proc
- New retention reconcile state updates partman.part_config.retention
  from postgres.telegraf.retention_days on every apply
- so_telegraf_trim cron is now unconditionally absent; script stays on
  disk as a manual fallback
2026-04-16 17:27:15 -04:00
..
2025-12-02 11:16:08 -06:00
2025-12-11 17:30:06 -05:00
2025-12-02 11:16:08 -06:00
2026-03-23 16:26:56 -04:00
2026-04-09 10:18:36 -04:00
2026-04-06 15:08:30 -05:00
2026-04-09 10:18:36 -04:00
2025-10-30 11:02:36 -04:00
2026-03-06 15:45:36 -05:00
2026-03-19 14:39:10 -04:00
2026-03-19 14:41:49 -04:00
2026-01-07 14:14:57 -05:00
2026-03-23 14:04:48 -05:00
2025-10-14 11:03:00 -04:00
2026-03-19 14:46:49 -04:00