New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 910561 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
emaxx@chromium.org
pmarko@chromium.org
█ bartfab@chromium.org
pbond@chromium.org
█ lamzin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-3
Hotlist-2
Hotlist-1


Sign in to add a comment

diagnostics: implement a gRPC API to run command tools to gather OS info for diagnistics_processor

Project Member Reported by pbond@chromium.org, Nov 30 
Implement a gRPC API to run the next command tools to gather OS info for diagnostics_processor if available:

OS Info:
osb_release
uname

Hostname:
hostname

Battery info:
dmidecode

Bluetooth info:
hciconfig

Comment 1 by emaxx@chromium.org, Nov 30 

RE dmidecode: IIRC, it always returns a subset of data from raw DMI tables, but we already planned to return the complete DMI tables as a file dump of /sys/firmware/dmi/tables/ via the GetSysfsData() call. So if that plan holds, then I guess we won't need a special API for the battery info from dmidecode.

Comment 2 by pbond@chromium.org, Jan 10

Components: Enterprise
►

Sign in to add a comment