chore: cleanup extraneous logging (#9156)

* The batchstats warning went out on every Ctrl+C in my development

Rule of silence:

The provisioner and connect messages messages were sent out on every startup
without a corresponding user event, making them annoying and more-so
debug messages.
This commit is contained in:
Ammar Bandukwala
2023-08-17 21:01:55 +00:00
committed by GitHub
parent 9710bada06
commit be40dc85ab
5 changed files with 12 additions and 6 deletions
+2 -2
View File
@@ -124,8 +124,8 @@ for deploying the Coder server.
--values provisioner-values.yaml
```
You can verify that your provisioner daemons have successfully connected to Coderd by looking for a log with message
`provisionerd successfully connected to coderd` from each Pod.
You can verify that your provisioner daemons have successfully connected to Coderd by looking for a debug log message that says
`provisionerd: successfully connected to coderd` from each Pod.
## Example: Running an external provisioner on a VM