Add a datacenter resource. #1413
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The purpose of this is to allow for people running in a hybrid environment.
hdost
force-pushed
the
feat/1458-adding-datacenter-convention
branch
from
1ae444e
to
eb6b348
Compare
jsuereth
requested changes
Sep 18, 2024
|
|
||
| # Datacenter | ||
|
|
||
| ## Datacenter Attributes |
There was a problem hiding this comment.
We have tooling to autogenerate markdown, you should use <!-- semconv datacenter --> here for consistency.
See: https://github.com/open-telemetry/semantic-conventions/blob/main/model/README.md
| @@ -0,0 +1,15 @@ | |||
| groups: | |||
| - id: datacenter | |||
There was a problem hiding this comment.
This needs a name field, set it to datacenter for now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The purpose of this is to allow for people running in a hybrid environment.
Relates #1409
Changes
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]