Releases: instana/go-sensor
v1.13.0
This minor release includes the following fixes & improvements:
- An instrumented HTTP client now maintains and sends the W3C Trace Context headers
- An instrumented HTTP handler picks up Instana trace from W3C Trace Context even if the upstream is not monitored by Instana
- HTTP calls that have
X-Instana-Synthetic
set are now marked as synthetic and will be filtered out from the default "Analyze Calls" view. This might be useful to exclude such service calls as health checks or pings from overall metrics.
v1.12.1
This patch release includes the following fixes & improvements:
- W3C Trace Context headers sent to an instrumented handler are propagated with each outgoing HTTP request made with instrumented HTTP client to ensure trace continuation.
v1.12.0
This minor release includes the following fixes & improvements:
- Propagate W3C Trace Context headers sent to an instrumented handler to ensure that an existing trace is not terminated after passing through an Instana-instrumented HTTP server.
- Calls to an instrumented server resulting with HTTP 500 and above are now marked as errors in the dashboard.
v1.11.0
This minor release includes the following fixes & improvements:
- Fixed a data race that allowed the autoprofiler to keep running multiple samplers concurrently in rare cases.
- Added support for
X-Instana-L
header that defines the tracing level for a service. The upstream service can now suppress tracing by sendingX-Instana-L=0
. Any span started from such trace context will not be sent to the agent. - Added
instana.SuppressTracing()
span option to suppress trace beginning from the current call. - The
http.Client
instrumentation does not initiate traces anymore by not creating exit spans without a parent. - The existing HTTP headers used for Instana trace context propagation with non-canonical MIME names are now removed before injecting the context.
- Minor fixes to the README code examples.
instrumentation/instagrpc/v1.0.3
This patch release includes the following fixes & improvements:
- Client interceptors don't create spans if there was no parent span provided to avoid initiation of a trace that starts with an exit span
- Reduced the error span payload sent to the agent by removing the redundant
message
field - Minor formatting improvements to the log messages written by instrumentation code
instrumentation/instasarama/v1.0.0
This is the first release of github.com/Shopify/sarama
instrumentation for Instana. github.com/instana/go-sensor/instrumentation/instasarama
provides wrappers for Kafka consumers and producers that ensure trace context propagation via Kafka messages.
To use this module add following line to your go.mod:
require github.com/instana/go-sensor/instrumentation/instasarama v1.0.0
For detailed usage example consult the README or check the Examples section of package documentation.
v1.10.0
This minor release includes the following fixes & improvements:
- Spans containing log messages with
error.object
field keys are treated as erroneous - Added support for batched spans: the number of operations executed within one span can be attached to the agent span using the
instana.BatchSize
tag
v1.9.1
This patch release includes minor documentation fixes & improvements:
- Refactored span kind detection so it can be defined for a particular span type only
instrumentation/instagrpc/v1.0.2
This patch release includes minor documentation fixes & improvements:
- GRPC spans are now being sent in a registered span format
- Server and client instrumentation are now using
(*instana.Sensor.)Logger()
to output diagnostic messages - The minimum version of
github.com/instana/go-sensor
required forinstagrpc
has been changed tov1.9.0
v1.9.0
This minor release includes the following fixes & improvements:
- HTTP, GRPC and Kafka spans are now sent in a registered span format that contains only predefined set of tags. Please consult the godoc for the list of supported tags for each span type
- Span
error
andlang
fields were removed, as they are not supported by Instana anymore