Problem: Prometheus Trace Files Fill Up /tmp in 1.18

[mwinter-alliance]

Expected behaviour

The disk doesn't fill with dozens of Prometheus trace files every second.

Current behaviour

/tmp/prometheus-statshga72cj1 fills up with files owned by archivematica named:

counter_704803.db counter_711150.db gauge_livesum_700388.db gauge_livesum_706924.db gauge_livesum_713259.db histogram_702681.db histogram_709026.db histogram_715362.db
counter_704804.db counter_711153.db gauge_livesum_700390.db gauge_livesum_706925.db gauge_livesum_713260.db histogram_702683.db histogram_709029.db histogram_715363.db
counter_704809.db counter_711157.db gauge_livesum_700392.db gauge_livesum_706926.db gauge_livesum_713263.db histogram_702685.db histogram_709031.db histogram_715365.db
counter_704814.db counter_711159.db gauge_livesum_700416.db gauge_livesum_706927.db gauge_livesum_713266.db histogram_702687.db histogram_709033.db histogram_715367.db
counter_704816.db counter_711161.db gauge_livesum_700418.db gauge_livesum_706928.db gauge_livesum_713268.db histogram_702689.db histogram_709035.db histogram_715370.db
counter_704820.db counter_711167.db gauge_livesum_700420.db gauge_livesum_706931.db gauge_livesum_713270.db histogram_702692.db histogram_709036.db histogram_715375.db
counter_704824.db counter_711170.db gauge_livesum_700422.db gauge_livesum_706932.db gauge_livesum_713271.db histogram_702696.db histogram_709038.db histogram_715377.db
counter_704834.db counter_711173.db gauge_livesum_700424.db gauge_livesum_706935.db gauge_livesum_713273.db histogram_702698.db histogram_709040.db histogram_715380.db
counter_704835.db counter_711176.db gauge_livesum_700426.db gauge_livesum_706938.db gauge_livesum_713276.db histogram_702701.db histogram_709045.db histogram_715385.db
counter_704836.db counter_711186.db gauge_livesum_700429.db gauge_livesum_706940.db gauge_livesum_713277.db histogram_702703.db histogram_709048.db histogram_715388.db
counter_704837.db counter_711187.db gauge_livesum_700431.db gauge_livesum_706942.db gauge_livesum_713280.db histogram_702705.db histogram_709051.db histogram_715389.db
counter_704839.db counter_711188.db gauge_livesum_700433.db gauge_livesum_706943.db gauge_livesum_713282.db histogram_702706.db histogram_709055.db histogram_715397.db

[...]
Steps to reproduce

Unsure. Possibly tied to a failed characterization step. Have not seen this issues before 1.18

Your environment (version of Archivematica, operating system, other relevant details)

1.18 Ubuntu Linux 22.04

---

For Artefactual use:

Before you close this issue, you must check off the following:

• All pull requests related to this issue are properly linked
• All pull requests related to this issue have been merged
• A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
• Documentation regarding this issue has been written and merged (if applicable)
• Details about this issue have been added to the release notes (if applicable)

[liptakpanna]

We had the same issue, setting limits on Prometheus had no effect.
We had to disable Prometheus, it also caused memory (RAM) spikes.