&gt; Metrics are fetched over HTTP by Prometheus, and they usually don&#x27;t come from files. You&#x27;d either have Prometheus scrape each job individually, or scrape your controller daemon that&#x27;d attach a labels indicating the job of each metric.<p>I was thinking more of the data model (<a href="https:&#x2F;&#x2F;prometheus.io&#x2F;docs&#x2F;concepts&#x2F;data_model&#x2F;" rel="nofollow">https:&#x2F;&#x2F;prometheus.io&#x2F;docs&#x2F;concepts&#x2F;data_model&#x2F;</a>). Specifically, from <a href="https:&#x2F;&#x2F;prometheus.io&#x2F;docs&#x2F;practices&#x2F;naming&#x2F;" rel="nofollow">https:&#x2F;&#x2F;prometheus.io&#x2F;docs&#x2F;practices&#x2F;naming&#x2F;</a> , &quot;Remember that every unique key-value label pair represents a new time series, which can dramatically increase the amount of data stored. Do not use labels to store dimensions with high cardinality (many different label values), such as user IDs, email addresses, or other unbounded sets of values.&quot;. So in our case the job ID would be such an unbounded value..?