From 073854bc9953c1ff873f450c548097b5a564ecba Mon Sep 17 00:00:00 2001 From: Joe White Date: Tue, 21 Jul 2020 15:22:58 -0400 Subject: [PATCH] Update the utilization metric description to be less terrible. Removed some of the nonsensical language from the description and unremoved some less unsensible test. --- configuration/datawarehouse.d/ref/Jobs-statistics.json | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/configuration/datawarehouse.d/ref/Jobs-statistics.json b/configuration/datawarehouse.d/ref/Jobs-statistics.json index 3059aaf9ff..1387100758 100644 --- a/configuration/datawarehouse.d/ref/Jobs-statistics.json +++ b/configuration/datawarehouse.d/ref/Jobs-statistics.json @@ -266,7 +266,9 @@ "aggregate_formula": { "$include": "datawarehouse.d/include/Jobs-util-agg.sql" }, - "description_html": "The percentage of the ${ORGANIZATION_NAME} obligation of a resource that has been utilized by ${ORGANIZATION_NAME} jobs.
${ORGANIZATION_NAME} Utilization: The ratio of the total CPU hours consumed by ${ORGANIZATION_NAME} jobs over a given time period divided by the total CPU hours that the system is contractually required to provide to ${ORGANIZATION_NAME} during that period. It does not include non-${ORGANIZATION_NAME} jobs.
It is worth noting that this value is a rough estimate in certain cases where the resource providers don't provide accurate records of their system specifications, over time.", + "description_html": "The percentage of core time that a resource has been running jobs.
${ORGANIZATION_NAME} Utilization: The ratio of the total CPU hours consumed by jobs over a given time period divided by the maximum CPU hours that the system could deliver (based on the number of cores present +on the resources). This value does not take into account downtimes or outages. It is just calculated based on the number of cores in the resource +specifications.", "name": "${ORGANIZATION_NAME} Utilization", "precision": 2, "timeseries_formula": {