-
Notifications
You must be signed in to change notification settings - Fork 31
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: improve robustness of custom service naming #416
feat: improve robustness of custom service naming #416
Conversation
❌ @basti1302 the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a
Git even has a
|
8009291
to
6dfc017
Compare
❌ @basti1302 the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a
Git even has a
|
Previously, we only added span.data.service to _entry_ spans (when the environment variable INSTANA_SERVICE_NAME is set). The requirements around this have changed, now we add this annotation to _all_ spans (but still only if it has been explicitly configured). Signed-off-by: Bastian Krol <bastian.krol@ibm.com>
6dfc017
to
8db23aa
Compare
LGTM |
Previously, we only added span.data.service to entry spans (when the environment variable INSTANA_SERVICE_NAME is set). The requirements around this have changed, now we add this annotation to all spans (but still only if it has been explicitly configured).
See also: