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

Make span_kind required in yaml and break down multi-kind span definitions #1513

Open
lmolkova opened this issue Oct 23, 2024 · 0 comments
Open
Labels
tooling Regarding build, workflows, build-tools, ...

Comments

@lmolkova
Copy link
Contributor

Following spans (after #1512) would remain kindless as they describe multiple kinds of spans (or it's not clear what it should be)

  • span.rpc.connect_rpc
  • span.rpc.grpc
  • span.rpc.jsonrpc
  • span.faas
  • span.faas.datasource
  • span.faas.timer
  • span.messaging
  • span.aws.lambda

We should break them down and describe individual kinds (as they have different attribute sets and identities)

@lmolkova lmolkova added the tooling Regarding build, workflows, build-tools, ... label Oct 23, 2024
@lmolkova lmolkova moved this to Clean up YAML schema in Semantic Conventions Tooling Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Regarding build, workflows, build-tools, ...
Projects
Status: Clean up YAML schema
Development

No branches or pull requests

1 participant