Bug 93754 - optionally log all D-Bus traffic to the systemd Journal
Summary: optionally log all D-Bus traffic to the systemd Journal
Status: RESOLVED MOVED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: git master
Hardware: Other All
: medium enhancement
Assignee: D-Bus Maintainers
QA Contact: D-Bus Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-18 11:10 UTC by Simon McVittie
Modified: 2018-10-12 21:26 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Simon McVittie 2016-01-18 11:10:21 UTC
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).
Comment 1 GitLab Migration User 2018-10-12 21:26:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/139.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.