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

Ensure the consistency of signal names #1121

Closed
codeboten opened this issue Feb 11, 2022 · 1 comment · Fixed by #1706
Closed

Ensure the consistency of signal names #1121

codeboten opened this issue Feb 11, 2022 · 1 comment · Fixed by #1706
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@codeboten
Copy link
Contributor

codeboten commented Feb 11, 2022

Currently Trace/Tracing/Traces, Metrics, and Logging/Logs are used in various places to name the OpenTelemetry signals. It would be great to ensure these are named consistently at least in the status section for each language implementation.

Edit (@chalin): for context, see #1116 (comment).

@svrnm
Copy link
Member

svrnm commented Aug 30, 2022

While I agree with this, I don't see a way to get this fix besides going through all pages and double check if those terms are used properly (if I crawl for "Tracing" I get matches for "OpenTracing" and there is some places where "Tracing" might be the right term, same for Logs & Logging)

Looks like something we have to fix gradually, so I tag this with "help wanted" and "good first issue" hoping for some help :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants