[SERVER-19799] provide ASIO handler tracking hooks backed by the mongo logger Created: 06/Aug/15  Updated: 06/Dec/22  Resolved: 29/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Adam Midvidy Assignee: Backlog - Service Architecture
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22433 Include more helpful logging for ASIO... Closed
Assigned Teams:
Service Arch
Sprint: Platform 8 08/28/15, Platform 9 (09/18/15)
Participants:

 Description   

ASIO includes a useful feature that allows custom log hooks to be compiled in to track handler events such as creation, completion invocation start, and invocation end.

The default implementation logs to std::cout, but there is a mechanism to allow custom hooks to be used by defining some macros (see handler_tracking.hpp).

We should define ASIO_CUSTOM_HANDLER_TRACKING in debug builds, add log hooks at some verbosity level > 1, and probably add a new log component as it will be very, very chatty.



 Comments   
Comment by Adam Midvidy [ 21/Sep/15 ]

unfortunately the release of ASIO we have (development 1-11-1) does not support custom handler tracking. The master branch of ASIO has it, but we should probably wait until there is a release.

Generated at Thu Feb 08 03:52:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.