screenshot of Bustle 0.3.1

Bustle is a better dbus-monitor! It records and draws sequence diagrams of D-Bus activity, showing signal emissions, method calls and their corresponding returns, with timestamps for each individual event and the duration of each method call. This can help you check for unwanted D-Bus traffic, and pinpoint why your D-Bus-based application isn't performing as well as you like. It also provides statistics like signal frequencies and average method call times.

You might enjoy these slides on profiling and optimizing D-Bus APIs, presented at the Gran Canaria Desktop Summit, which introduce Bustle and discuss where it might be useful.

Bustle 0.4.8 (2015-03-22)

Three still frames of a demo video

Older news

Getting Bustle

Using Bustle

Run it:


Now click File → New… to start recording session bus traffic. When you're done, click Stop, and explore the log.

If you want to record traffic without running the UI (maybe on an embedded platform which doesn't have Gtk+ and/or a Haskell compiler), you can use the stand-alone logger:

bustle-pcap logfile.bustle

You can then open logfile.bustle in Bustle.

You can also get some ASCII-art version of the statistics shown in the UI:

bustle --count logfile.bustle
bustle --time logfile.bustle

If you want to log all system bus traffic, you need to edit /etc/dbus/system.conf to enable eavesdropping, and then remove the include of /etc/dbus-1/system.conf.d which seems to re-enable strictness. Then you can run the stand-alone logger against the system bus:

bustle-pcap --system system-log.bustle

Please remember to undo these changes when you're done.


Bustle is written and maintained by Will Thompson (to a great extent courtesy of Collabora Ltd.), with contributions by Dafydd Harries, Marc Kleine-Budde, Sergei Trofimovich, Chris Lamb, Alex Merry, Cosimo Alfarano, Philip Withnall and Αποστολίδου Χρυσαφή. It was inspired by a similar tool by Alban Crequy. Patches, feature requests, bug reports and cakes are welcome!