common: always include priority in perf counter dump

JSON output with inconsistent sets of members is
annoying to use on the receiving side.

Signed-off-by: John Spray <john.spray@redhat.com>
(cherry picked from commit e631f1a72735ec618e2f3012ad7b9c5830d6c0eb)

diff --git a/src/common/perf_counters.cc b/src/common/perf_counters.cc
index f3bc4e37860f759c78a7dbb7b60cc49809ea42f3..d73a1b9ea07afe35f9f06a8cd09c39b5b53c3b8f 100644 (file)
--- a/src/common/perf_counters.cc
+++ b/src/common/perf_counters.cc
@@ -396,12 +396,10 @@ void PerfCounters::dump_formatted_generic(Formatter *f, bool schema,
       } else {
         f->dump_string("nick", "");
       }
-      if (d->prio) {
-       int p = std::max(std::min(d->prio + prio_adjust,
-                                 (int)PerfCountersBuilder::PRIO_CRITICAL),
-                        0);
-       f->dump_int("priority", p);
-      }
+      int p = std::max(std::min(d->prio + prio_adjust,
+                                (int)PerfCountersBuilder::PRIO_CRITICAL),
+                       0);
+      f->dump_int("priority", p);
       f->close_section();
     } else {
       if (d->type & PERFCOUNTER_LONGRUNAVG) {