)]}'
{
  "commit": "49493c5bb1fd3b66ed1e4c6b5c82f2b4ccda0cf6",
  "tree": "d81bfe40f064042f4cb92b00046f7ce571e41947",
  "parents": [
    "a6b3b7498569ca09fa4ddffe880afb0528a606ee"
  ],
  "author": {
    "name": "Saša Živkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Wed Feb 05 17:31:16 2020 +0100"
  },
  "committer": {
    "name": "Saša Živkov",
    "email": "zivkov@gmail.com",
    "time": "Fri Feb 14 12:21:15 2020 +0000"
  },
  "message": "Use JmxReporter.Builder.filter to handle exclusion rules\n\nSince the support for excluding some metrics from being reported was\nadded in Ib4da8ba8ad5d6ba3f1cbb0b3f83375cfcef3af67, this metric reporter\nwas broken: it computed the set of metrics to be exposed once and then\nexposed this fixed (sub)set forever. Any newly added metrics were not\nexposed. For example: if a plugin which exposes metrics loads after this\nplugin, these metrics would be exposed via JMX. Further, even some\nmetrics bound via a MetricModule in Gerrit core wouldn\u0027t be reported by\nthis plugin if that MetricModule (which is also a LifeCycleModule)\nhappens to receive its start() call after this plugin already computed\nthe snapshot of exposed metrics.\n\nInstead of copying the set of exposed metrics in a new MetricRegistry,\napply a MetricFilter to the MetricRegistry instance from Gerrit core.\nHandle exclusion rules through that filter.\n\nChange-Id: Iaf0b4fa03293ccc2313ab0332f70a3a41ea30a25\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "947481444375406508ebe4a3f823cfaeb7605a12",
      "old_mode": 33188,
      "old_path": "src/main/java/com/googlesource/gerrit/plugins/metricsreporterjmx/GerritJmxReporter.java",
      "new_id": "c8453627d2ba69c86890e88fa5bca9d99f2d6044",
      "new_mode": 33188,
      "new_path": "src/main/java/com/googlesource/gerrit/plugins/metricsreporterjmx/GerritJmxReporter.java"
    }
  ]
}