-
Notifications
You must be signed in to change notification settings - Fork 158
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
Common socket connection conventions #454
Comments
11 tasks
jack-berg
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 7, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
AlexanderWert
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 10, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
jack-berg
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 16, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
jack-berg
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 16, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
jsuereth
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 16, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
jsuereth
pushed a commit
to jack-berg/semantic-conventions
that referenced
this issue
Nov 16, 2023
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
jsuereth
pushed a commit
that referenced
this issue
Nov 16, 2023
Fixes #454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
this was accidentally auto-closed (via merging an old commit that closed spec issue number 454) |
joaopgrassi
pushed a commit
to dynatrace-oss-contrib/semantic-conventions
that referenced
this issue
Jan 10, 2024
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
joaopgrassi
pushed a commit
to dynatrace-oss-contrib/semantic-conventions
that referenced
this issue
Jan 10, 2024
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
pyohannes
pushed a commit
to pyohannes/semantic-conventions
that referenced
this issue
Jan 17, 2024
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
pyohannes
pushed a commit
to pyohannes/semantic-conventions
that referenced
this issue
Jan 17, 2024
Fixes open-telemetry#454 Related to #3337 As the Messaging SIG merged its last OTEP 222, we will be adding operations that require Links after Span creation, taking a direct route with `AddLink()`, albeit without any of the new members suggested in #3337, e.g. `timestamp` (to be discussed in a separate issue). ``` AddLink(spanContext, attributes /* optional */) ```
2 tasks
3 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Connection-level instrumentation is useful for all kinds of protocols to detect/investigate any connectivity issues, optimize connection pools, detect leaks, etc. The following telemetry signals are common across protocols:
The conventions could include:
We should be able to reuse
network.*
and other existing common attributes to define generic connection conventions.Individual protocols on top of sockets may extend such conventions and add protocol-specific attributes (e.g. AMQP may define some other attributes, spans/metrics).
Socket connection conventions should be reused across databases, http, messaging, and other conventions
See https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-metrics.md where we already define a bunch of metrics for DB connections specifically.
The text was updated successfully, but these errors were encountered: