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

Indicate which semantic conventions generate errors. #1003

Open
carlosalberto opened this issue Sep 25, 2020 · 0 comments
Open

Indicate which semantic conventions generate errors. #1003

carlosalberto opened this issue Sep 25, 2020 · 0 comments
Labels
area:error-reporting Related to error reporting area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory

Comments

@carlosalberto
Copy link
Contributor

As part of OTEP 136, and as a minor follow up to #966 we ought to

  • Indicate which semantic conventions generate errors.

Additional context.
OTEP PR: open-telemetry/oteps#136

@carlosalberto carlosalberto added area:semantic-conventions Related to semantic conventions area:error-reporting Related to error reporting release:after-ga Not required before GA release, and not going to work on before GA spec:miscellaneous For issues that don't match any other spec label labels Sep 25, 2020
@Oberon00 Oberon00 added spec:trace Related to the specification/trace directory and removed spec:miscellaneous For issues that don't match any other spec label labels Sep 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:error-reporting Related to error reporting area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA spec:trace Related to the specification/trace directory
Development

No branches or pull requests

2 participants