[Bug]: pulseV6, unified_resources.db growing, growing,...

[FabienD74]

Describe the bug

A few days ago, I found this DB at 2GB.
I shutdown pulse, perform a sqlite vacuum command, it shriked just a bit ( down to 1.5 GB).
Then found a table containing something like "traces of field values", with some timestamps more than 2 weeks ago.
As i'm running V6RC6, i decided to backup thix LXC ( to be 🦺 ), deleted unified_resources.*, and restarted.
Everything went smooth ( good surprise ;-) ).
DB recreated and started growing slowly.
Today tose files are

191M Jun 12 17:00 unified_resources.db
32K Jun 12 17:00 unified_resources.db-shm
4.1M Jun 12 17:01 unified_resources.db-wal

I don't know what's inside in this DB, but i think 2 little things are missing:

• a watchdog query: delete all lines in table(s) older than XX days)
• a vaccum job to keep it nice/small/healty.

Regards
Fabien

To reproduce

Just let pulse run couple of days...
Then look at files /data/resources/*

Expected behavior

Keep this DB under control :-)
OR i will have to create a job to stop pulse, delete it, restart pulse.

Pulse version

v6rc6

Agent version

none

Image tag or digest

rcourtman/pulse:6.0.0-rc.6

Installation type

Docker

Relevant logs or diagnostics

NA

Confirmations

• I verified the exact Pulse version and image reference from the running instance.
• I searched existing issues for duplicates.

[FabienD74]

I just realized: is this DB the new format of the old "metrics.db" ????
At the end of my system.json i have:

  "theme": "dark",
  "fullWidthMode": true,
  "allowEmbedding": true,
  "temperatureMonitoringEnabled": false,
  "dnsCacheTimeout": 300,
  "hideLocalLogin": false,
  "metricsRetentionRawHours": 1,
  "metricsRetentionMinuteHours": 2,
  "metricsRetentionHourlyDays": 2,
  "metricsRetentionDailyDays": 7,
  "disableDockerUpdateActions": false,
  "telemetryEnabled": false
}

As you can see i want extremely limited metrics ;-)