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

Bring otel resource into alignment #4050

Merged
merged 1 commit into from
Oct 17, 2023
Merged

Conversation

BrynCooke
Copy link
Contributor

Currently, we have telemetry.tracing.common.resources and telemetry.tracing.common.attributes.

These should be 'resource' to align with otel terminology.

Part of #4043


Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

  • Changes are compatible1
  • Documentation2 completed
  • Performance impact assessed and acceptable
  • Tests added and passing3
    • Unit Tests
    • Integration Tests
    • Manual Tests

Exceptions

Note any exceptions here

Notes

Footnotes

  1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.

  2. Configuration is an important part of many changes. Where applicable please try to document configuration examples.

  3. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions.

@BrynCooke BrynCooke requested a review from a team as a code owner October 17, 2023 15:34
Currently, we have telemetry.tracing.common.resources and telemetry.tracing.common.attributes.

These should be 'resource' to align with otel terminology.

Part of #4043
@BrynCooke BrynCooke force-pushed the bryn/attributes-resources branch from 408982e to 2c662f5 Compare October 17, 2023 15:35
@BrynCooke BrynCooke merged commit 1c5127b into dev Oct 17, 2023
2 checks passed
@BrynCooke BrynCooke deleted the bryn/attributes-resources branch October 17, 2023 16:08
@BrynCooke BrynCooke linked an issue Oct 17, 2023 that may be closed by this pull request
xuorig pushed a commit to Netflix-Skunkworks/router that referenced this pull request Oct 24, 2023
Currently, we have telemetry.tracing.common.resources and
telemetry.tracing.common.attributes.

These should be 'resource' to align with otel terminology.

Part of apollographql#4043

<!-- start metadata -->
---

**Checklist**

Complete the checklist (and note appropriate exceptions) before the PR
is marked ready-for-review.

- [ ] Changes are compatible[^1]
- [ ] Documentation[^2] completed
- [ ] Performance impact assessed and acceptable
- Tests added and passing[^3]
    - [ ] Unit Tests
    - [ ] Integration Tests
    - [ ] Manual Tests

**Exceptions**

*Note any exceptions here*

**Notes**

[^1]: It may be appropriate to bring upcoming changes to the attention
of other (impacted) groups. Please endeavour to do this before seeking
PR approval. The mechanism for doing this will vary considerably, so use
your judgement as to how and when to do this.
[^2]: Configuration is an important part of many changes. Where
applicable please try to document configuration examples.
[^3]: Tick whichever testing boxes are applicable. If you are adding
Manual Tests, please document the manual testing (extensively) in the
Exceptions.

Co-authored-by: bryn <[email protected]>
xuorig pushed a commit to Netflix-Skunkworks/router that referenced this pull request Oct 24, 2023
Currently, we have telemetry.tracing.common.resources and
telemetry.tracing.common.attributes.

These should be 'resource' to align with otel terminology.

Part of apollographql#4043

<!-- start metadata -->
---

**Checklist**

Complete the checklist (and note appropriate exceptions) before the PR
is marked ready-for-review.

- [ ] Changes are compatible[^1]
- [ ] Documentation[^2] completed
- [ ] Performance impact assessed and acceptable
- Tests added and passing[^3]
    - [ ] Unit Tests
    - [ ] Integration Tests
    - [ ] Manual Tests

**Exceptions**

*Note any exceptions here*

**Notes**

[^1]: It may be appropriate to bring upcoming changes to the attention
of other (impacted) groups. Please endeavour to do this before seeking
PR approval. The mechanism for doing this will vary considerably, so use
your judgement as to how and when to do this.
[^2]: Configuration is an important part of many changes. Where
applicable please try to document configuration examples.
[^3]: Tick whichever testing boxes are applicable. If you are adding
Manual Tests, please document the manual testing (extensively) in the
Exceptions.

Co-authored-by: bryn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bring existing config into alignment between tracing and metrics
2 participants