Hello,
I am currently looking into building a data pipeline for our chrome extension (not yet implemented, but will be used for the initial milestone) that will facilitate this extension to report certain app usage and other health related metrics (unavailable in chrome today, but can be derived from the extension) in relation to our
Contact Center efforts. I have drafted a preliminary
design spec listing all possible options for building this pipeline. I just realized we will most likely not be able to leverage Mojo IPC for reporting this data because of the way the receivers are
bound to the extension thereby leaking access to other extensions that may be sharing the process with ours, so we will have to leverage an extension API that is limited to just our extension for this purpose. As I was going through the API
proposal doc, I realized the general recommendation was for all new APIs to be public by default, but given the fact that this new API would report data to our internal servers, I was not sure if it'd make sense for this API to be public. I figured I'd get some inputs from folks who were familiar with the access level for scenarios like these before I even started with the initial design proposal for this API.
My initial assumption is that this API would live under the
reporting namespace and reuse some of our pre-existing
protos that are currently being used internally within chrome for reporting purposes, as inputs to this new API. We can then transmit these records through our pre-existing reporting pipeline from there. If there are other alternatives that I might have abruptly missed out on, please do let me know. :)
