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
In principle there is no reason that receivers and exporters that use gRPC can't share the code to handle the gRPC configuration settings. This will enforce consistency and saves some code duplication.
Example: currently Jaeger gRPC exporter doesn't have a timeout or can use secure via configuration, however, the OC exporter has all these settings.
In principle there is no reason that receivers and exporters that use gRPC can't share the code to handle the gRPC configuration settings. This will enforce consistency and saves some code duplication.
Example: currently Jaeger gRPC exporter doesn't have a timeout or can use secure via configuration, however, the OC exporter has all these settings.
Related: #219 (comment)
The text was updated successfully, but these errors were encountered: