(PE-38408) Add additional PuppetDB metrics

Based on discussion with Austin Blatt these additional metrics could be
helpful in diagnosing issues with PuppetDB.

> The reports.process, catalog.save and facts.save metrics would likely be
> useful as they are the highest level metrics closest to "how long did the
> puppetdb terminus take?".
>
> puppetdb.payload.format would be good to include as well in case our json
> conversion is slow. We do have to do some string manipulation there, so it
> isn't just Ruby's to_json function.
>
> I'm less familiar with the terminus's use for querying, but I imagine
> puppetdb.query, puppetdb.facts.find, and puppetdb.facts.search would be
> good to include assuming those terminus functions are used somewhere.

Author: justinstoller

src/java/com/puppetlabs/puppetserver/MetricsPuppetProfiler.java

@@ -136,9 +136,11 @@ private void updateMetricsTrackers(String[] metricId, Map<String, Timer> metrics
 
                 if (
                     ("resource".equals(secondElement) && "search".equals(thirdElemet)) ||
-		    ("facts".equals(secondElement) && "encode".equals(thirdElemet)) ||
-		    ("catalog".equals(secondElement) && "munge".equals(thirdElemet)) ||
-		    ("report".equals(secondElement) && "convert_to_wire_format_hash".equals(thirdElemet))
+		    ("payload".equals(secondElement) && "format".equals(thirdElemet)) ||
+		    // Set.of would be preferrable but 7.x still support Java 8, which does not have Set.of
+		    ("facts".equals(secondElement) && Arrays.asList("save", "find", "search", "encode").contains(thirdElemet)) ||
+		    ("catalog".equals(secondElement) && Arrays.asList("save", "munge").contains(thirdElemet)) ||
+		    ("report".equals(secondElement) && Arrays.asList("convert_to_wire_format_hash", "process").contains(thirdElemet))
 		) {
                     String key = String.join(".", secondElement, thirdElemet);
                     Timer metric = metricsByID.get(getMetricName(sliceOfArrayToList(metricId, 3)));