Add Semantic conventions for TLS/SSL encrypted communication#2992
Add Semantic conventions for TLS/SSL encrypted communication#2992svrnm wants to merge 43 commits intoopen-telemetry:mainfrom
Conversation
Signed-off-by: svrnm <[email protected]>
Signed-off-by: svrnm <[email protected]>
Signed-off-by: svrnm <[email protected]>
Signed-off-by: svrnm <[email protected]>
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
@open-telemetry/specs-approvers any feedback?:) |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
anything missing, any additional feedback? |
|
Now that the ECS OTEP was merged, do we also want maybe to adopt the attributes from there for these? https://www.elastic.co/guide/en/ecs/current/ecs-tls.html |
@joaopgrassi |
@joaopgrassi thx for bringing that up here! @svrnm check out open-telemetry/semantic-conventions#1012 and #3409 for some examples, and see if it makes sense to rename the new attributes you've proposed to align with the ECS names. We will bring over ECS attributes more proactively in the future, but for now we just want to avoid new divergence in cases where alignment makes sense. |
|
@joaopgrassi , @trask thank you! I gave it a try, a few notable changes:
|
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
joaopgrassi
left a comment
There was a problem hiding this comment.
LGTM, thanks for putting the effort on this!
About the array attributes, I think we should be OK in adding them, as there's already some conventions using it like
I'm not an expert in this, so I don't know how crucial those array attributes are, but I guess the goal is to take over all ECS attributes. @trask @AlexanderWert what do you think?
Signed-off-by: svrnm <[email protected]>
Signed-off-by: svrnm <[email protected]>
Signed-off-by: svrnm <[email protected]>
I added certificate and certificate_chain now, please give it a look. |
|
@svrnm heads up - most likely this PR will be closed, and we'll ask you to resubmit the PR in a new repo, please refer to #3474 (comment). |
I assumed that, let me find some time to bring it over to the new semconv repo! |
Fixes #1652
Changes
Add trace/span semantic conventions for TLS/SSL.
I created a similar PR (#1854) a long while back that stalled eventually, I wanted to give it another try. Before doing so I did some scrubbing, added some references, removed some things where I was uncertain and updated a few things to match the APIs or RFCs (e.g. "not_before" and "not_after" are used for validity instead of valid_from and valid_to)
Reference implementation: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-net/src/instrumentation.ts#L121
References: