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
I am currently exploring the traces API in OTel, and have found that the Span class is important in traces. However, this class is designed with a key-value based API that requires us to assign properties via key-value pairs. This approach makes it difficult for us to maintain the schema of our telemetry in our code. Previously, we were able to define events in a protocol schema file (such as Protocol Buffer) and use the generated code file throughout our codebase.
I am wondering if OTel provides a similar solution that would allow us to:
Maintain our event schema with an IDL and organize them effectively.
Generate code based on these IDL files and use it in our code.
Build events based on 2 and convert them to Spans easily.
I would appreciate any ideas or suggestions you may have. Thank you!
The text was updated successfully, but these errors were encountered:
However, this class is designed with a key-value based API that requires us to assign properties via key-value pairs.
This is exactly the design of OTLP.
I am wondering if OTel provides a similar solution that would allow us to:
Maintain our event schema with an IDL and organize them effectively.
Generate code based on these IDL files and use it in our code.
Build events based on 2 and convert them to Spans easily.
A protocol with stronger-typed attributes for spans is probably possible but that would be a different protocol, I don't think it can be supported in OTLP.
Hi OTel team,
I am currently exploring the traces API in OTel, and have found that the
Span
class is important in traces. However, this class is designed with a key-value based API that requires us to assign properties via key-value pairs. This approach makes it difficult for us to maintain the schema of our telemetry in our code. Previously, we were able to define events in a protocol schema file (such as Protocol Buffer) and use the generated code file throughout our codebase.I am wondering if OTel provides a similar solution that would allow us to:
I would appreciate any ideas or suggestions you may have. Thank you!
The text was updated successfully, but these errors were encountered: