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

Explain the source of registry files #1204

Open
yurishkuro opened this issue Jul 3, 2024 · 0 comments
Open

Explain the source of registry files #1204

yurishkuro opened this issue Jul 3, 2024 · 0 comments
Labels
bug Something isn't working tooling Regarding build, workflows, build-tools, ...

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Jul 3, 2024

Area(s)

No response

What happened?

Description

I am trying to debug what happened to otel.library.name attribute. I was only able to find it in

| `otel.library.name` | string | | `io.opentelemetry.contrib.mongodb` | ![Deprecated](https://img.shields.io/badge/-deprecated-red)<br>use the `otel.scope.name` attribute. |

The file itself contains a header:

<!-- NOTE: THIS FILE IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
<!-- see templates/registry/markdown/attribute_namespace.md.j2 -->

While the template name is marginally useful, I would much rather know the source of the generated file. Can we please include that in the header?

Semantic convention version

1.26.0

Additional context

No response

@yurishkuro yurishkuro added bug Something isn't working triage:needs-triage labels Jul 3, 2024
@lmolkova lmolkova added tooling Regarding build, workflows, build-tools, ... and removed triage:needs-triage labels Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tooling Regarding build, workflows, build-tools, ...
Projects
Development

No branches or pull requests

3 participants