Releases: instana/go-sensor
Releases · instana/go-sensor
v1.15.0
This minor release includes the following fixes & improvements:
- Added
instana.SQLOpen()
,instana.InstrumentSQLDriver()
andinstana.WrapSQLConnector()
methods to instrument calls to an SQL database made withdatabase/sql
. - The README has been restructured for readability
v1.14.1
v1.14.0
This minor release includes the following fixes & improvements:
- Added support for tracing services running in AWS Fargate. See the README.md on how to configure in-app sensor to send metrics to a serverless agent.
- Fixed an issue causing two services appearing under the same process when running services with custom name configured via
instana.Options{}
in containerized environments
v1.13.2
This patch release includes the following fixes & improvements:
- AutoProfile™ can now be activated via an env variable
v1.13.1
This patch release includes the following fixes & improvements:
- Address an issue with not seeing calls in Instana dashboard, when an HTTP request comes from an unmonitored service to a service that is instrumented via OpenTracing API
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