-
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
Add 'meta.refinery.local_hostname' to all spans #250
Conversation
Hurm. I tried it out locally, and I'm not seeing the extra metadata on the events. I think the |
Urgh, thank you and my apologies! :\ Adding the field before the builder is created (or on the builder directly) does give the desired result, but it breaks the testsuite as the field is being added all the event data. If you feel this is useful -- I think it's a helpful addition -- perhaps it should be a config option anyway? Then it can be disabled for the testsuite to avoid having to add the field to all the expected test results. Perhaps something like |
No worries! It wasn't intuitive to me, either. I like the idea of adding a config option, because there's already something akin to it: Does that make sense? |
Makes good sense to me! I'll pick that up and run with it. 🚀 |
Currently just adding 'meta.refinery.local_hostname' to all spans. The intention with this (and any additional) field is to assist in troubleshooting issues with a single Refinery instance.
1744d72
to
d798009
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.
Question about the default value, and small update about live reload, otherwise LGTM!
@jharley could you update the docs as well? https://docs.honeycomb.io/manage-data-volume/refinery/configuration/#general-configuration |
No problem! |
New config option AddHostMetadataToTrace Currently just adding 'meta.refinery.local_hostname' to all spans. The intention with this (and any additional) field is to assist in troubleshooting issues with a single Refinery instance.
The intention is to help determine issues with a single Refinery instance.