4 Commits

Author	SHA1	Message	Date
Dmytro Kozlov	fc5292d8ed	app/vmctl: add verbose output for docker installations or when TTY isn't available (#4333) ... * app/vmctl: add verbose output for docker installations or when TTY isn't available * app/vmctl: fix tests * app/vmctl: make vmctl interactive if no tty * app/vmctl: cleanup * app/vmctl: add comment --------- Co-authored-by: Nikolay <nik@victoriametrics.com>	2023-06-02 14:57:08 +02:00
Dmytro Kozlov	6a794ec5d5	app/{vmctl,vmalert}: update progress bar library (make vendor-update) (#3138) ... * app/{vmctl,vmalert}: update progress bar library (make vendor-update) * app/{vmctl,vmalert}: make vendor-update	2022-09-21 11:08:33 +03:00
Dmytro Kozlov	c8af625bcc	vmctl: fix build for solaris os (#2555) ... * vmctl: fix build for solaris os * vmctl: updated dependency (using Syscall instead of Syscall6) * vmctl: updated dependency * vmctl: updated dependency	2022-05-09 21:36:18 +02:00
Dmytro Kozlov	b2294d1cf1	vmctl/vm: added datapoints collection bar (#2486) ... add progress bars to the VM importer The new progress bars supposed to display the processing speed per each VM importer worker. This info should help to identify if there is a bottleneck on the VM side during the import process, without waiting for its finish. The new progress bars can be disabled by passing `vm-disable-progress-bar` flag. Plotting multiple progress bars requires using experimental progress bar pool from github.com/cheggaaa/pb/v3. Switch to progress bar pool required changes in all import modes. The openTSDB mode wasn't changed due to its implementation, which implies individual progress bars per each series. Because of this, using the pool wasn't possible. Signed-off-by: dmitryk-dk <kozlovdmitriyy@gmail.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>	2022-05-02 09:06:34 +02:00