-
Notifications
You must be signed in to change notification settings - Fork 95
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
feat: Add configuration for trace and parent ID field names #630
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.
This is close! A few changes, please. Although I originally specified spanID, I think we should leave it off for now since it's unused; we can always add it later.
I had also thought about putting these configurations down a level under a parent key, but decided that too should wait for the config revamp. It's fine the way it is.
…n IDs and parent span Ids Signed-off-by: Davin Taddeo <davin@honeycomb.io>
Signed-off-by: Davin Taddeo <davin@honeycomb.io>
Signed-off-by: Davin Taddeo <davin@honeycomb.io>
Signed-off-by: Davin Taddeo <davin@honeycomb.io>
39bdf23
to
a59f38c
Compare
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 is great. Thank you.
🎉 Thank you all! This is useful to us |
Which problem is this PR solving?
#626 - Make trace fields configurable
Short description of the changes
This should make trace, span, and parent ID fields configurable, which will allow refinery to work where a client uses a non-standard trace ID field name.
Fixes #626.