Oliver Hookins

@telendt I guess that's just a simpler version of this: https://github.com/prometheus/client_golang/blob/master/prometheus/http.go#L296-L306

@streadway are you ok with me making a PR for report along the lines of #28 ? Or perhaps @telendt is kind enough to add report to the same PR...

We're not using the elastic CI stack, although the config files we are using for systemd agent termination, and the agent settings themselves to set that up are directly taken...

``` 2021-11-12 02:11:29 INFO ip-10-10-128-133-1 All agents have been idle for 1543 seconds. Disconnecting... 2021-11-12 02:11:29 INFO ip-10-10-128-133-1 Disconnecting... sleeping for 10 seconds before terminating instance to allow agent logs...

OK, have tracked down the issue a bit closer. I'm wondering whether this may actually be an agent fault. Here is the last bit of the log from the agent...

Sadly enabling debug doesn't shed any more light on the issue. ``` 2021-11-15 03:33:28 INFO ip-10-10-130-161-1 All agents have been idle for 1593 seconds. Disconnecting... 2021-11-15 03:33:28 INFO ip-10-10-130-161-1 Disconnecting......

There's no `--verbose` so I've used log level 5, hopefully that's enough for you. ``` Error: 1 build task(s) failed! at Object.handleProcessResults (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/commands/base.ts:532:19) at BuildCommand.action (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/commands/build.ts:148:12) at GardenCli.runCommand (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/cli/cli.ts:498:20) at...

Maybe a first step on the path to deprecation would be to fix this: ``` Failed resolving provider kubernetes. Here is the output: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Error validating provider configuration: key .certManager.email...

Probably not worth solving if certmanager is going to be removed anyway. Stalebot can close it.

@eysi09 would still like this to be solved, as `garden delete environment` means we have to trash our letsencrypt private key, and I'm still worried about hitting rate limits there....