This is a meta issue, which means that it is used to collect all the issues related to the feature it is tracking (the Extension Activity Logging feature in this case).
The issues currently linked to this meta are related to implementing the ActivityLog API (which also required changes to the WebExtensions internals to notify to the ActivityLog API the extension activity served by the WebExtensions internals, e.g. Bug 1542403, and in the future it may require more changes to the DOM API internals to be able to notify other kind of activities, Bug 1558366), more issues will be filed and linked to this one to track the additional work needed to expose the feature to the users (e.g. the work on the UI side).
(In reply to Ajitesh from comment #3)
So basically, we will try to track all the activated extensions in the browser in real time, like their network requests, altered browser setting etc. And display all this to user.
Am i correct? Please let me know, if i am wrong.
yes, as part of some new bugzilla issues linked as dependencies of this meta issue, an "Extension Activity Logging" UI should be created (e.g. prototyped as a privileged extension), which should allow the users of this UI to decide what kind of activity to collect, and then allow the user to further analyze/filter/save/load these logs.
(In reply to Ajitesh from comment #4)
Also, Are there any planning for the UI development ?
Providing the ActivityLog API is clearly only one part of the entire "Extension Activity Logging" feature, to make these logs useful we also need to expose it to people (e.g. to allow a reviewer or a security researcher to analyze this logs) and/or other services (e.g. to be also analyzed and processed automatically in other ways).
Some UI development will definitely be necessary, e.g. to expose these logs to the "class of users" that are going to be interested into it (developers, reviewers, and sophisticated users as aswan pointed out in comment 2)