Use same logger structure as bbb-html5 #231
Description
Is your feature request related to a problem? Please describe.
The SDK's logger uses the same logging library as BigBlueButton does.
However, its implementation differs significantly: different target streams, format, serializer etc.
It'd be useful if the SDK's logger followed BBB's for multiple reasons:
- Re-using an established logging pattern is good for both developers and admins who have worked on log post-processing systems for bbb-html5
- Having the ability to send log entries to remote endpoints
- Pulling BBB logging configs (e.g.: endpoint, log levels, target streams) in case a plugin doesn't have its own override configuration
Describe the solution you'd like
Rework the plugin logger to be similar - if not exactly equal - to bbb-html5's logger.
See https://github.com/bigbluebutton/bigbluebutton/tree/v3.0.x-release/bigbluebutton-html5/imports/startup/client/logger.
This includes: streams, serializers, formats, primitives, console behavior.
Plugin loggers should also:
- Have a static log metadata field (e.g.:
plugin) which carries the plugin's name.- That metadata field should be appended at the start of console messages and should be sent in a machine-readable format in remote streams
- Pull logger configuration from the web client for the general scenario: https://github.com/bigbluebutton/bigbluebutton/blob/ed612d3d2f2e7b323a4c2668ad0e5659a70e35f4/bigbluebutton-html5/private/config/settings.yml#L1148-L1160
- Have a way to override the above configs at the plugin/manifest level (e.g.: "we want the overall system to be logLevel: INFO, but plugin X to be DEBUG")
Describe alternatives you've considered
None