Infrastructure at your Service

Dear IT colleagues,

We regularly have to read log file contents either to understand software functioning or for debugging purpose.

Most of the time we access same log files located in same servers.

It is very painful to login every time, then lookup and extract relevant traces for a particular case under investigation.

On top of that, especially on some systems, there is no Unix “tail” command equivalent.

For all these reasons, I want to share with you a software I created to speed up these recurrent operations: DBI Tail.


It is Java based, so it can potentially run on every operating systems.

Agent-less for distant access to file content (SSH tunnel for Linux, shared drive for Windows servers)

Live colourization support for highlighting most relevant traces.

It includes stop, start, pause, clean, save, zoom, search features and so on. It also can automatically detect character encoding of files for better display quality.


Once your files are configured within DBI Tail, access to their live content takes only few seconds. It constantly makes me saving time, and is ready and mature enough to be shared with you now.

It is Free and Open Source.

Binary and source code are available on Github. please just follow the link:

Please feel free to ask for any question or submit new enhancement requests.








  • Sašo says:

    I would realy like to try your tool, but I just can seem to configure it correctly.
    I’m trying to connect to a server via ssh with a cert, but I just get an error:

    error: connecting to host: com.jcraft.jsch.JSchException: Auth fail.

    Is there an option to view application log, to see if the settings are set correctly?

    • Philippe Schweitzer says:

      Hi Saso,

      Thanks for looking at dbi Tail.

      The tail is designed to work with an SSH public key. So please make sure having generated your public key accordingly in the server side.

      To enable more verbose logging, I first invite you to download a full package within the Github repository, then look at the documentation which describes all steps how to achieve your demand.

      Finally, I also invite you to look at the server side logs eventually to also find more potential issue traces.

      Have a nice day,


Leave a Reply

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

Middleware Team
Middleware Team