cloudquery
cloudquery copied to clipboard
Logs: Add startup logs to help debug throttling stuff
trafficstars
Is your feature request related to a problem? Please describe.
We encounter a lot of throttling errors. It'd be great if on startup of cloudquery we could log a bunch of related info to help debug it:
- memory on the machine
- ullimits (soft + hard)
- kernel "open file" limits
also version
Add them to cmd/root.go:logInvocationParams or make another fn and call it from rootCmd.PersistentPreRunE just like logInvocationParams is called.
Im closing this for now and we can reopen once we will get those issues again given a lot was changed including more consistent logging and concurrency.