The Go Driver had a user inquire about adding an operation command to CommandSucceededEvent/CommandFailedEvent. The reason for why we don't do this is addressed in INT-76. This PR suggests extending the specifications to include this information in a Q&A section.
Additionally, the headers for this file appear to be incorrectly structured per the rst docs, causing a runtime error when trying to add a section with correct formatting:
command-logging-and-monitoring.rst:35: (SEVERE/4) Title level inconsistent:
Removed use cases of ---\nx\n--- and replaced with just ---. Updated subsections to use ^.
Please complete the following before merging:
[x] Update changelog.
[ ] Make sure there are generated JSON files from the YAML test files.
[ ] Test changes in at least one language driver.
[ ] Test these changes against all server versions and topologies (including standalone, replica set, sharded clusters, and serverless).
The Go Driver had a user inquire about adding an operation command to CommandSucceededEvent/CommandFailedEvent. The reason for why we don't do this is addressed in INT-76. This PR suggests extending the specifications to include this information in a Q&A section.
Additionally, the headers for this file appear to be incorrectly structured per the rst docs, causing a runtime error when trying to add a section with correct formatting:
Removed use cases of
---\nx\n---and replaced with just---. Updated subsections to use^.Please complete the following before merging: