| commit | b65280ff745c47dbb1e668e68e156bf3de6b6e93 | [log] [tgz] |
|---|---|---|
| author | Sui Chen <suichen@google.com> | Tue Jun 30 18:14:03 2020 -0700 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Fri Oct 29 01:12:53 2021 +0000 |
| tree | f435a175ab3c8b37035227a91059511c07734897 | |
| parent | 1800ed4d798fdb26013cfbbead7e28afc7a96c65 [diff] |
dbus-vis: Initial commit dbus-vis visualizes PCAP files captured by busctl as well as text-format outputs from busctl. dbus-vis displays the visualized results in horizontal timelines, where each horizontal bar represents a DBus request, or an IPMI request (an IPMI request is a specific kind of DBus request sent to the IPMI daemon.) The requests may be grouped by one or more fields including type, sender, destination, path, interface, member. In addition, if the BMC console is available, dbus-vis can connect to the BMC console and capture DBus/IPMI requests in real time. dbus-vis is in the form of a web page and is wrapped using Electron to run as a desktop app. Basic usage: * Mouse click and drag: * If mouse is over time axis: drag timeline horizontally * If mouse is over vertical scroll bar: scroll up/down * Otherwise: select a region for measuring time & zooming in * Mouse Scroll wheel: * If mouse is over time axis: zoom in/out * Otherwise: scroll up/down * Click on the expandable headers will expand/collapse the entries under that particular header. Signed-off-by: Sui Chen <suichen@google.com> Change-Id: I863c2ba80025d10efb44fd12868e37912fae9a47
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.
Please use gerrit for all patches to this repository:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.
So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.
We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.
There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.
