Announcing Sysdig 0.1.85
The main new feature is sysdig completion for bash and zsh.
What this means is that from now on you don’t have to look at the manual constantly when using sysdig, and you can just press the TAB key any time you’re struggling remembering the syntax, and the possible alternatives will come up, like in this bash example:
gianluca@sid:~$ sysdig --list[Tab] --list --list-chisels --list-events
Or, even cooler, with zsh you can see a whole bunch of “dynamic” things:
gianluca@sid~% sysdig -c[Tab] bottlenecks -- Slowest system calls echo_fds -- Print the data read and written by processes. fdbytes_by -- I/O bytes, aggregated by an arbitrary filter field fdcount_by -- FD count, aggregated by an arbitrary filter field fileslower -- Trace slow file I/O iobytes -- Sum of I/O bytes on any type of FD iobytes_file -- Sum of file I/O bytes iobytes_net -- Show total network I/O bytes list_login_shells -- List the login shell IDs netlower -- Trace slow network I/0 proc_exec_time -- Show process execution time ...
As you can see, the support for zsh is much nicer than the bash one, it automatically completes chisels and filter fields! We gladly welcome patches from the community to bring the bash completion at the same level!
In order to use this, if you install sysdig through our binary repository, the completion files are already installed under /usr/share/zsh/vendor-completions/_sysdig and /etc/bash_completion.d/sysdig, so the majority of the distributions will automatically use them by default. If you install sysdig from sources, “make install” will put them in /usr/local/share/zsh/vendor-completions/_sysdig and /usr/local/etc/bash_completion.d/sysdig, so you might have to tweak a bit your shell to get access to it, as usual.
Community support is available on the sysdig mailing list.
Bugs and issues can be submitted through github.
Btw, we are running a webinar discussing the challenges of troubleshooting issues and errors in Docker containers and Kubernetes, like pods in CrashLoopBackOff, join this session and learn:
- How to gain visibility into Docker containers with Sysdig open source and Sysdig Inspect.
- Demo: troubleshoot a 502 Bad Gateway error on containerized app with HAproxy.
- Demo: troubleshoot a web application that mysteriously dies after some time.
- Demo: Nginx Kubernetes pod goes into CrashLoopBackOff, what's you can do? Will show you how to find the error without SSHin into production servers.
Start Your Free Trial Today