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
Our otel trace export requires grpc at the moment. However, there are otel collectors out there that don't support grpc and only support plain http. One example is https://axiom.co/ which a user reported here https://discord.com/channels/1128210118216007792/1277162136610541602/1277162136610541602. To also integrate with these otel collectors, we probably need to make the protocol that the SpanExporter uses configurable (http vs grpc). Bonus points if we also add TLS support for the http exporter. What's not clear is whether Axiom requires http with json payload or understands protobuf messages.
The text was updated successfully, but these errors were encountered:
With this commit, it is now possible to choose which protocol the OTEL
exporter uses to export the traces. Users can choose grpc or protobuf
over http.
This fixesrestatedev#2361.
Our otel trace export requires grpc at the moment. However, there are otel collectors out there that don't support grpc and only support plain http. One example is https://axiom.co/ which a user reported here https://discord.com/channels/1128210118216007792/1277162136610541602/1277162136610541602. To also integrate with these otel collectors, we probably need to make the protocol that the
SpanExporter
uses configurable (http vs grpc). Bonus points if we also add TLS support for the http exporter. What's not clear is whether Axiom requires http with json payload or understands protobuf messages.The text was updated successfully, but these errors were encountered: