You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/weaver registry resolve -r ../opentelemetry-specification/semantic_conventions -f yaml
⠇ Resolving registry `../opentelemetry-specification/semantic_conventions`Diagnostic report:
× The semantic convention spec is invalid (path_or_url: "../opentelemetry-specification/semantic_conventions/
│ trace/http.yaml"). groups[2].attributes: data did not match any variant of untagged enum AttributeSpec at line
│ 135 column 7
Total execution time: 0.100291173s
I believe the issue comes from requirement_level: optional used for one of the attributes. This is not a variant supported by Weaver. My experience with SemConv isn't extensive enough to know if this variant was removed or renamed, but that's probably what happened. If necessary, we could add this variant and issue a warning. @MadVikingGod and @jsuereth What do you think?
I would do an exploration of this. If this is the only problem stopping us from parsing v1.18 and any other before, then yes, I would try to fix it. But if this just uncovers more issues, it's probably not a path worth pursuing.
Add this information to the documentation.
The text was updated successfully, but these errors were encountered: