optionally log all D-Bus traffic to the systemd Journal
Submitted by Simon McVittie
Assigned to D-Bus Maintainers
In a development environment, it's useful to be able to gather diagnostics for the whole system into one place.
D-Bus traffic is a useful way to monitor API boundaries. It would be nice to have something a little more structured and scalable than
sudo systemd-cat dbus-monitor --system systemd-cat dbus-monitor --session
One possibility is to log to the systemd Journal, perhaps with a human-readable summary of the message header in the standard MESSAGE field, and the raw bytes of the D-Bus message in a new binary field, DBUS_MESSAGE or something.
This could either be an optional feature of dbus-daemon, or of dbus-monitor (with sample systemd system and user units to start it, not enabled by default).
Version: git master