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
{{ message }}
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.
I am trying to get up and running sending traces from an existing Spring Cloud Sleuth instrumented Spring Boot application to honeycomb-opentracing-proxy and it is failing with the following error in the proxy console:
time="2019-10-25T02:51:55Z" level=info msg="error unmarshaling spans" error="json: cannot unmarshal bool into Go struct field binaryAnnotation.value of type string" type=application/json
Spring Boot Version: 2.1.3.RELEASE
Spring Cloud Sleuth Version: 2.1.1.RELEASE
I am running the open tracing proxy with the following docker command:
docker run -p 9411:9411 honeycombio/honeycomb-opentracing-proxy -k $KEY -d $DATA_SET
From reading the documentation the honeycomb-opentracing-proxy only supports v1 of the JSON API so I have explicitly set that in spring cloud config as this appears to default to v2.
it looks like this is not completely implementing the v1 format (that's what the marshaling error is about). there are "address annotations" which are semantically the same as span.remoteEndpoint in v2 format.
Here's an example of "sa" which is "server address" on a client span:
Hi All,
I am trying to get up and running sending traces from an existing Spring Cloud Sleuth instrumented Spring Boot application to honeycomb-opentracing-proxy and it is failing with the following error in the proxy console:
Spring Boot Version: 2.1.3.RELEASE
Spring Cloud Sleuth Version: 2.1.1.RELEASE
I am running the open tracing proxy with the following docker command:
From reading the documentation the honeycomb-opentracing-proxy only supports v1 of the JSON API so I have explicitly set that in spring cloud config as this appears to default to v2.
application.properties
Any help would be greatly appreciated. Also raised on Stack Overflow here
The text was updated successfully, but these errors were encountered: