-
Notifications
You must be signed in to change notification settings - Fork 245
DRIVERS-719 OpenTelementry specification #1826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…logy. Adding toplogy requirements for transaction tests
- `driver_operation_name db.collection_name` if the command is executed on a collection (e.g., | ||
`findOneAndDelete warehouse.users`). | ||
- `db.driver_operation_name` if there is no specific collection for the command (e.g., `warehouse.runCommand`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks inconsistent. Why the driver_operation_name
is at the beginning for a collection operation and at the end for a database operation?
One of this would be more consistent:
warehouse.users.findOneAndDelete
andwarehouse.runCommand
findOneAndDelete warehouse.users
andrunCommand warehouse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The naming follows the design document. We can revisit though 👍 https://docs.google.com/document/d/1182STFDVkQ6ixy1iCWZROC5K-Ef4M3aV__5--WXB7DI/edit?tab=t.0#heading=h.2s9zdv6a57gn
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GromNaN: Note the same inconsistency exists in the Instrumenting Server Commands > Span Name section below. I'd be in favor of using the operation/command name as the initial prefix and then appending the database or full namespace as appropriate.
|
||
Spans SHOULD have the following attributes: | ||
|
||
| Attribute | Type | Description | Requirement Level | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
db.client.connection.pool.name
is not listed. Is it because it doesn't have the "stable" flag? It would be easy to fill when the connection is created by an ODM, they usually have a connection name.
- `driver_operation_name db.collection_name` if the command is executed on a collection (e.g., | ||
`findOneAndDelete warehouse.users`). | ||
- `db.driver_operation_name` if there is no specific collection for the command (e.g., `warehouse.runCommand`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GromNaN: Note the same inconsistency exists in the Instrumenting Server Commands > Span Name section below. I'd be in favor of using the operation/command name as the initial prefix and then appending the database or full namespace as appropriate.
source/unified-test-format/tests/invalid/expectedTracingSpans-spanMalformedMissingName.yml
Outdated
Show resolved
Hide resolved
source/unified-test-format/tests/invalid/expectedTracingSpans-spanMalformedMissingName.yml
Outdated
Show resolved
Hide resolved
source/unified-test-format/tests/invalid/expectedTracingSpans-spanMalformedTagsMustBeObject.yml
Outdated
Show resolved
Hide resolved
source/unified-test-format/tests/invalid/expectedTracingSpans-spanMalformedTagsMustBeObject.yml
Outdated
Show resolved
Hide resolved
- `enableCommandPayload`: Optional boolean. When set to `true`, enables capturing of command payload details in | ||
tracing spans. | ||
- If `true`, the test runner SHOULD capture detailed command payload information in tracing spans. | ||
- If `false` or omitted, the test runner SHOULD exclude command payload details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realize this impacts the test runner, but should it also refer to configuring the MongoClient to enable tracing?
Co-authored-by: Jeremy Mikola <[email protected]>
Co-authored-by: Jeremy Mikola <[email protected]>
…TracingMessages-additionalProperties.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedTagsMustBeObject.yml Co-authored-by: Jeremy Mikola <[email protected]>
…TracingMessages-additionalPropertyType.yml Co-authored-by: Jeremy Mikola <[email protected]>
…missingPropertySpans.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedMissingName.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedTagsMustBeObject.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedAdditionalProperties.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedNestedMustBeArray.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedMissingName.yml Co-authored-by: Jeremy Mikola <[email protected]>
…spanMalformedMissingTags.yml Co-authored-by: Jeremy Mikola <[email protected]>
Co-authored-by: Jeremy Mikola <[email protected]>
Co-authored-by: Jeremy Mikola <[email protected]>
DRIVERS-719
observeTracingMessages
andexpectTracingMessages