-
Notifications
You must be signed in to change notification settings - Fork 57
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
Contextual tracer from multi-tenancy #769
Conversation
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.
LGTM
) | ||
|
||
const ( | ||
attributeNameTenantID = "tenant_id" |
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.
@wbrowne any opionins on the name? The runner currently uses stackID
in its own spans:
However OTEL suggests using snake_case:
https://opentelemetry.io/docs/specs/otel/common/attribute-naming/
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.
Yeah fair 👍 We can update that in the runner side, and maybe keep stackID
/stackId
for the logs
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.
👍
What this PR does / why we need it:
Adds
tenant_id
span attribute to all spans created by the default tracer.Which issue(s) this PR fixes:
Fixes to #724
Special notes for your reviewer: