[DRIVERS-2167] Add compression information to command monitoring events Created: 14/Dec/18  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Matt Broadstone Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Driver Changes: Needed

 Description   

It might be useful to be able to see whether a command is being compressed, and which compression type is being used if so. This would have helped a lot in HELP-8442



 Comments   
Comment by Jeffrey Yemin [ 17/Dec/18 ]

I have generally been against adding anything to command monitoring that exposes wire protocol implementation details.  As the spec says:

This specification intends to abstract the wire protocol so listeners receive similar events no matter what version of MongoDB the driver is connected to

This also limits driver implementation options, as it requires that a driver implement command monitoring at an abstraction layer that is compression-aware.

That said, I'm not totally opposed. Just not convinced yet.

Comment by Rathi Gnanasekaran [ 14/Dec/18 ]

Someone will need to investigate to determine if compression would be know at the time APM is dispatched. 

Generated at Thu Feb 08 08:24:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.