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.

Sign up for GitHub

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

Jump to bottom

Chinese translation for opentelemetry specs,docs #201

Closed
sunface opened this issue Aug 1, 2019 · 1 comment
Closed

Chinese translation for opentelemetry specs,docs #201

sunface opened this issue Aug 1, 2019 · 1 comment

Comments

@sunface
Copy link
Member

sunface commented Aug 1, 2019 •
edited
Loading

Hi all:
Great work on OpenTelemetry!

We are a translation team from china, and we sincerely want to translate OpenTelemetry's specs,docs to chinese to make more people knowing and using opentelemetry in the future.

Our work has already begun: https://github.com/opentelemetry-cn(cn is short for china), so if you have any questions or suggestions, please notify us, and we will do better later.
@sunface sunface changed the title Chinese translation for opentelemetry Chinese translation for opentelemetry specs,docs Aug 1, 2019
@sunface
Copy link
Member Author

sunface commented Aug 1, 2019

reopen in open-telemetry/community

@sunface sunface closed this as completed Aug 1, 2019
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 21, 2024
@tigrannajaryan @carlosalberto
Introduce Scope Attributes (open-telemetry#201)
9282884 
* Introduce Scope Attributes

There are a few reasons why adding Scope attributes is a good idea:
- There are 2 known use cases where Scope attributes can solve specific problems:
  - Add support for [Meter "short_name"](open-telemetry#2422),
    represented as an attribute of Meter's Scope.
  - Add support for differentiating the type of data emitted from the scopes that belong
    to different data domains, e.g. profiling data emitted as log records or client-side
    data emitted as log records needs to be differentiated so that it can be easily
    routed and processed differently in the backends. We don't have a good way to handle
    this today. The type of the data can be recorded as an attribute Logger's Scope.
- It makes Scope consistent with the other primary data types: Resource, Span, Metric,
  LogRecord.

See additional [discussion here](open-telemetry#2450).
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 23, 2024
@tigrannajaryan
Introduce Scope Attributes (open-telemetry#201)
637991d 
* Introduce Scope Attributes

There are a few reasons why adding Scope attributes is a good idea:
- There are 2 known use cases where Scope attributes can solve specific problems:
  - Add support for [Meter "short_name"](open-telemetry#2422),
    represented as an attribute of Meter's Scope.
  - Add support for differentiating the type of data emitted from the scopes that belong
    to different data domains, e.g. profiling data emitted as log records or client-side
    data emitted as log records needs to be differentiated so that it can be easily
    routed and processed differently in the backends. We don't have a good way to handle
    this today. The type of the data can be recorded as an attribute Logger's Scope.
- It makes Scope consistent with the other primary data types: Resource, Span, Metric,
  LogRecord.

See additional [discussion here](open-telemetry#2450).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sunface