Bash tips & tricks [ep. 4]: Use logging levels

This is the fourth epidose of a small series.


Support different logging levels natively in your scripts so that your code will be more stable and maintainable.




Nothing to invent, there are already a few blog posts around about the best practices for log messages. I personally like the one from Michael Wayne Goodman:

I have reused his code in my scripts with very few modifications to fit my needs:

The edumpvar is handy to have the status of several variables at once:

If you couple the verbosity level with input parameters you can have something quite clever (e.g. -s for silent, -V for verbose, -G for debug). I’m putting everything into one single snippet just as example, but as you can imagine, you should seriously put all the fixed variables and functions inside an external file that you will systematically include in your scripts:





It does not take into account the output file. That will be part of the next tip 🙂

The following two tabs change content below.


Oracle ACE Director and Computing Engineer at CERN
Ludovico is an Oracle ACE Director, frequent speaker and community contributor, working as Computing Engineer at CERN, the European Organization for Nuclear Research, in Switzerland.

One thought on “Bash tips & tricks [ep. 4]: Use logging levels

  1. Pingback: Bash tips & tricks [ep. 4]: Use logging levels - Ludovico Caldara - Blogs - triBLOG

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.