Files
securityonion/salt/telegraf
Mike Reeves 9fe53d9ccc Use JSONB for Telegraf fields/tags to avoid 1600-column limit
High-cardinality inputs (docker, procstat, kafka) trigger ALTER TABLE
ADD COLUMN on every new field name, and with all minions writing into
a shared 'telegraf' schema the metric tables hit Postgres's 1600-column
per-table ceiling quickly. Setting fields_as_jsonb and tags_as_jsonb on
the postgresql output keeps metric tables fixed at (time, tag_id,
fields jsonb) and tag tables at (tag_id, tags jsonb).

- so-stats-show rewritten to use JSONB accessors
  ((fields->>'x')::numeric, tags->>'host', etc.) and cast memory/disk
  sizes to bigint so pg_size_pretty works
- Drop regex/regexFailureMessage from telegraf_output SOC UI entry to
  match the convention upstream used when removing them from
  mdengine/pcapengine/pipeline; options: list drives validation
2026-04-16 17:02:21 -04:00
..
2026-03-06 15:45:36 -05:00
2023-05-01 15:21:31 -04:00
2026-03-20 09:19:22 -04:00
2023-05-11 12:14:30 -04:00
2026-03-18 10:38:15 -04:00
2023-05-11 12:12:25 -04:00
2026-03-06 15:45:36 -05:00
2026-03-19 15:12:47 -04:00
2023-05-11 12:12:25 -04:00
2026-03-16 15:57:15 -04:00