[SERVER-56433] Replace use of boost::log to support logv2 Created: 28/Apr/21  Updated: 06/Dec/22  Resolved: 10/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Backlog - Security Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Assigned Teams:
Server Security
Participants:

 Description   

The boost::log library was initially selected as a backend for the logv2 implementation because the early design for that project included the ability to log as either text or JSON, and the pluggable formatter support in boost::log was appealing, Subsequent design changes dropped that requirement, and we only log in JSON now, so we aren't actually using the pluggable formatter support.

This wouldn't matter at all, except that we had to make local changes to boost::log in order for it to work correctly for us, see SERVER-46008.

These local boost changes represent an ongoing maintenance burden when we need to upgrade boost, in tickets like SERVER-44079. Furthermore, it means that users who build the product from source and use the --use-system-boost option (and people actually do this) will get a logging system with different behavior.

Since we no longer need the full functionality of boost::log to implement our logging support, we should replace our usage of it with something else.


Generated at Thu Feb 08 05:39:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.