Skip to content
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

Merged

Conversation

basti1302
Copy link
Contributor

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:

@basti1302 basti1302 marked this pull request as draft March 6, 2023 07:08
@github-actions
Copy link

github-actions bot commented Mar 6, 2023

@basti1302 the signed-off-by was not found in the following 1 commits:

  • 8009291: feat: improve robustness of custom service naming

📝 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 required

The 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:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

@basti1302 basti1302 force-pushed the add-service-annotation-to-all-spans-not-only-entries branch from 8009291 to 6dfc017 Compare March 6, 2023 07:19
@github-actions
Copy link

github-actions bot commented Mar 6, 2023

@basti1302 the signed-off-by was not found in the following 1 commits:

  • 6dfc017: feat: improve robustness of custom service naming

📝 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 required

The 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:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

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>
@basti1302 basti1302 force-pushed the add-service-annotation-to-all-spans-not-only-entries branch from 6dfc017 to 8db23aa Compare March 6, 2023 07:22
@basti1302 basti1302 marked this pull request as ready for review March 6, 2023 07:23
@basti1302 basti1302 requested a review from a team March 6, 2023 07:24
@Ferenc-
Copy link
Collaborator

Ferenc- commented Mar 6, 2023

LGTM

@Ferenc- Ferenc- merged commit 1376e67 into master Mar 6, 2023
@Ferenc- Ferenc- deleted the add-service-annotation-to-all-spans-not-only-entries branch March 6, 2023 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants