The status endpoint (/status/v1/services/puppetdb-status) now implements trapperkeeper-status levels, in particular specifying `level=critical` can make the query notably less expensive by avoiding any database queries. Currently, the `:status` will just be `null` when the level is critical.
The status endpoint (/status/v1/services/puppetdb-status) now implements the trapperkeeper-status levels, in particular specifying level `critical`. Previously the endpoint only supported the defaultlevel= `info`. The `critical` can make level only returns the query notably less `state` and the `service_version` of PuppetDB and avoids potentially expensive by avoiding any database queries. Currently, the The `:status` will just be is always `null` when. For queries that only require the `state` and `service_version`, specifying ` level is= critical` as a query parameter can make the query notably less expensive.