job name tagging in telemetry should be less specific for periodic jobs (should not include /periodic-1235... info)

[margueritepd]

Nomad version

0.8.4

Operating system and Environment details

Ubuntu 16.04

Issue

I'm trying to use Nomad telemetry, eg nomad.client.allocs.running, in datadog. I would like to monitor that my periodic job successfully runs on an ongoing basis. According to the docs, this metric is tagged with the job-name, which should in theory allow me to filter the metric by the name of my job and see job runs over time. However, in practice, the job tag includes the periodic run ID (for lack of a better term) (eg job:my-periodic-job/periodic-123456789). In datadog, I am not able to add a wildcard after the /. This very specific tagging makes it impossible to view runs for this job over time.

Additionally, according to datadog best practice, tags shouldn't originate from unbounded sources such as epoch timestamp. I'm keeping my fingers crossed that I don't get a stern email from them in the future!

Reproduction steps

Run a periodic job that runs every minute, observe the job tag of the statsd metrics emitted for nomad.client.allocs.running.

[Miserlou]

Related: #4422

[burdandrei]

sorted here: #4392

[stale]

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

[endocrimes]

Looks like this was fixed in #4392, closing now

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.