)]}'
{
  "log": [
    {
      "commit": "c2772c2984e4f29aa6032725e4f7d8680a54ed19",
      "tree": "be68d78a7eb1aaff15200705d4139dc616216318",
      "parents": [
        "aac6b6c7912b3feae4b68789508bee4bf1544731"
      ],
      "author": {
        "name": "Dan Smith",
        "email": "dansmith@redhat.com",
        "time": "Fri Apr 08 08:48:49 2022 -0700"
      },
      "committer": {
        "name": "Dan Smith",
        "email": "dansmith@redhat.com",
        "time": "Wed Apr 20 13:07:22 2022 -0700"
      },
      "message": "Gather performance data after tempest\n\nThis makes us gather a bunch of consistent statistics after we run\ntempest that can be use to measure the impact of a given change. These\nare stable metrics such as \"number of DB queries made\" and \"how much\nmemory is each service using after a tempest run.\"\n\nNote that this will always run after devstack to generate the JSON\nfile, but there are two things that control its completeness:\n\n - MYSQL_GATHER_PERFORMANCE must be enabled to get per-db stats\n - Unless tls-proxy is enabled, we will only get API stats for keystone\n\nChange-Id: Ie3b1504256dc1c9c6b59634e86fa98494bcb07b1\n"
    }
  ]
}