Conversation
| this._isConnecting = true; | ||
|
|
||
| this._logger.info(mongoLogId(1_001_000_014), 'Connecting', { | ||
| this._logger.info(mongoLogId(1_001_000_014), 'Connecting Started', { |
There was a problem hiding this comment.
I am inspired here by the driver's commandStarted/Succeeded/Failed. But the message changes aren't necessary so happy to undo.
There was a problem hiding this comment.
If the log id stays the same and conceptually it's the same event I think that's fine (but you will need to figure out all the tests that might be checking this 🙂)
|
|
||
| this._logger.info(mongoLogId(1_001_000_014), 'Connecting', { | ||
| this._logger.info(mongoLogId(1_001_000_014), 'Connecting Started', { | ||
| connectionId: this._id, |
There was a problem hiding this comment.
IIUC this _id is per attempt not per cluster, but that's fine for the use case in mms. LMK if "connectionId" isn't clear, I think its just important to not conflate that with a clusterId of some kind
|
What constitutes a fix/feat in compass? also happy to file a ticket for this for the history of it all. TIA! |
|
The "compass-e2e-tests__Logging_and_Telemetry_integration_after_running_an_example_path_through_Compass_log_events_for_the_critical_path.logs__Connecting_Succeeded" failure in CI looks legit (and we should have fixes in soon for other failures to make it less noisy), otherwise looks good!
We don't have very strict guides on this, |
d3813b8 to
77d1208
Compare
Description
https://jira.mongodb.org/browse/COMPASS-9404
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes