-
Notifications
You must be signed in to change notification settings - Fork 174
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
Session.id semantic convention #215
Conversation
Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>
Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>
Co-authored-by: Chengzhong Wu <legendecas@gmail.com>
ce4be2e
to
2574f89
Compare
d8c013b
to
1434ecf
Compare
- removed 'client' prefix - added session duration & start - removed behavior definitions of session
@open-telemetry/specs-approvers @open-telemetry/specs-semconv-maintainers This is ready for your review! |
We have 3 approvals on this and it's been open for months. |
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.
Usually in conventions, we also describe things like span names, maybe a structure of a trace (in this case modeling a session). Is this something the group discussed and want to work on? Or the idea is to just define the attribute for now?
I'm missing a bit more of context on why this change is needed. Is there any issue/meeting notes/discussion documented that could help understanding the need for this attribute?
Also please add a changelog entry.
@joaopgrassi respectfully, this has been discussed at length in the client SIG. Sessions don't really have a data shape themselves (or at least not yet in our mental model), it's more like a sequence of telemetry all grouped together, as identified by a session identifier. Hence this PR. The idea is to get something started so that we can iterate on it. This is not intended to be comprehensive yet. |
@breedx-splk all good, the concept of a session is clear to me. I was more interested in for example an issue where the SIG discussions and agreements/plans are documented. I don't participate in the SIG so having that piece of extra context IMO helps the general semconv approvers. |
This has several approvals and has been open for a while with no objections. Merging :) |
Discussed this in the client-side sig. Added a basic definition to start discussion.