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

Issue 746509 link

Starred by 1 user
Status: Assigned
Owner:
steve...@chromium.org
Cc:
█ tengs@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Consider merging PA_LOG and DEVICE_LOG

Project Member Reported by steve...@chromium.org, Jul 19 2017 
PA_LOG provides similar functionality to DEVICE_LOG (https://cs.chromium.org/chromium/src/components/device_event_log/device_event_log.h)

We should consider mapping PA_LOG ->

DEVICE_LOG(::device_event_log::LOG_TYPE_PA,
           ::device_event_log::LOG_LEVEL_##level)

Comment 1 by tengs@chromium.org, Jul 19 2017 

One other use of PA_LOG is allowing us to inspect the logs in chrome://proximity-auth.

Does DEVICE_LOG support an interface for our WebUI to fetch logs from the in-memory buffer?

Comment 2 by steve...@chromium.org, Jul 19 2017 

Yep, that's the purpose of DEVICE_LOG also. Entries are currently visible in chrome://device-log but there's no reason we couldn't continue to provide PA entries for chrome://proximity-auth.

https://cs.chromium.org/chromium/src/components/device_event_log/device_event_log_impl.cc?l=305

Comment 3 by zalcorn@chromium.org, Sep 28 

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 4 by weifangsun@chromium.org, Nov 8 

<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!
►

Sign in to add a comment