1. ores appears to be capturing worker-specific metrics at ores.<server_name>.uwsgi.worker.<worker id>.(...) The <worker id> field appears variable and unpredictable. Depending on the implementation, this could be the source of the ballooning usage and would contain sparse data (e.g. <worker id> being a thread number that has a short lifespan). Total in uwsgi alone: ~183,000 metrics.
2. zuul might be concerning, but evaluating usefulness of metrics might be worth considering. Each extension name in zuul.pipeline.(postmerge|gate-and-submit|test).mediawiki.extensions.<extension name> gets 18 metrics and appears to follow files. I imagine a situation where the metric becomes useless if an extension is removed, or renamed. Total ~39,000 metrics.
3. There are 637 servers no longer reporting data to servers.<hostname>.(...) and 577 of them do not appear in monitoring. It's possible the non-reporting but in monitoring nodes are due to T183454. Total: ~ 151,000 metrics.

I suggest two things:

1. Disable the ores uwsgi metrics collection.
2. Remove the hosts in servers.<hostname> that are dead or no longer reporting metrics.

I estimate at current rate of utilization the disk will be full in less than 15 days (unless there is a run on creates, then even less).