Releases: signalfx/signalfx-dotnet-tracing
Releases · signalfx/signalfx-dotnet-tracing
v0.2.3
General
- The release adds experimental support for AlwaysOn Profiling
Enhancements
- Add
SIGNALFX_PROFILER_LOGS_ENDPOINT
setting to configure the URL to where
logs are exported using OTLP/HTTP v1 log protocol. - Add
SIGNALFX_PROFILER_ENABLED
setting that enables AlwaysOn Profiling. - Add
SIGNALFX_PROFILER_CALL_STACK_INTERVAL
setting that overrides default
AlwaysOn Profiling sampling period. - Add zip release package for Windows
v0.2.2
General
- The release adds experimental support for automatic runtime and tracing metrics.
Enhancements
- Add
SIGNALFX_RUNTIME_METRICS_ENABLED
setting that enables runtime metrics. - Add
SIGNALFX_REALM
setting to let the instrumentation bypass
the OpenTelemetry Collector and send telemetry directly to Splunk
Observability Cloud ingest endpoints. - Add
SIGNALFX_METRICS_ENDPOINT_URL
setting that overrides
the metrics exporter's endpoint. - Add
SIGNALFX_TRACE_METRICS_ENABLED
setting that enables trace metrics.
v0.2.1
General
- Brings back support for Alpine Linux.
Bugfixes
- Fixes OpenTracing Scope creation when manual tracing is used.
v0.2.0
General
- The release contains significant changes as it is based on the latest
.NET Tracer for Datadog APM
with modifications to make it work with the
Splunk OpenTelemetry Collector
and directly with Splunk Observability Cloud.
Some of the changes are breaking. Please contact us if you miss any feature
from the previous release.
Breaking changes
- There is no support for .NET Framework older than .NET Framework 4.6.1.
- There is no support for Alpine Linux.
- There are no new releases for
SignalFx.Tracing
norSignalFx.Tracing.OpenTracing
NuGet packages. For manual instrumentation useOpenTracing
instead. You can find more information in the documentation. - Rename
SIGNALFX_DOTNET_TRACER_CONFIG_FILE
configuration toSIGNALFX_TRACE_CONFIG_FILE
. - Rename
SIGNALFX_PROPAGATOR
configuration toSIGNALFX_PROPAGATORS
. - Rename
SIGNALFX_TRACING_ENABLED
configuration toSIGNALFX_TRACE_ENABLED
- Rename
SIGNALFX_ASPNET_TEMPLATE_NAMES_ENABLED
configuration toSIGNALFX_TRACE_ROUTE_TEMPLATE_RESOURCE_NAMES_ENABLED
. - Remove
SIGNALFX_ADD_CLIENT_IP_TO_SERVER_SPANS
configuration.
New, fixed behavior is equivalent to flag enabled. - Remove
SIGNALFX_SYNC_SEND
configuration. - Remove
SIGNALFX_TRACE_DOMAIN_NEUTRAL_INSTRUMENTATION
configuration. - Remove
SIGNALFX_APPEND_URL_PATH_TO_NAME
configuration as it was against the
OpenTelemetry Semantic conventions for HTTP spans.
Take notice that the URL is available viahttp.url
tag. - Remove
SIGNALFX_USE_WEBSERVER_RESOURCE_AS_OPERATION_NAME
configuration.
New, fixed behavior is equivalent to flag enabled,
in order to better align with OpenTelemetry Semantic conventions for HTTP spans. - Remove
SIGNALFX_SANITIZE_SQL_STATEMENTS
configuration as all field
sanitizations are moving to the Splunk Distribution of OpenTelemetry Collector. - Remove
SIGNALFX_OUTBOUND_HTTP_EXCLUDED_HOSTS
configuration as
Splunk OpenTelemetry Collector
is the recommended place for spans filtering.
If you need span exclusion for specific URL substrings, it can be configured
usingSIGNALFX_TRACE_HTTP_CLIENT_EXCLUDED_URL_SUBSTRINGS
environment variable. - Remove
SIGNALFX_INSTRUMENTATION_ASPNETCORE_DIAGNOSTIC_LISTENERS
configuration
which is no longer needed. It provided a workaround for an issue in a specific
version of a library, which broke default instrumentation, and was already fixed. - Remove
SIGNALFX_SERVICE_NAME_PER_SPAN_ENABLED
configuration as
the OpenTelemetry specification
requires that the resources (such us as service)
have to be immutable. - Remove
SIGNALFX_INTEGRATIONS
. This configuration is not needed.
The instrumentation calledCallSite
was removed. - Deprecate
SIGNALFX_TRACE_LOG_PATH
. Please useSIGNALFX_TRACE_LOG_DIRECTORY
.
Enhancements
- Add Aerospike.Client
library instrumentation. - Add Microsoft.Data.SqlClient
andSystem.Data.SqlClient
library instrumentation. - Adopt OpenTelemetry Trace Semantic Conventions
in most of the instrumentations. - Add
SIGNALFX_HTTP_SERVER_ERROR_STATUSES
configuration that controls server
HTTP statuses to set spans as errors. - Add
SIGNALFX_HTTP_CLIENT_ERROR_STATUSES
configuration that controls client
HTTP statuses to set spans as errors. - Add
SIGNALFX_STDOUT_LOG_TEMPLATE
configuration that configuresstdout
template. - Add
SIGNALFX_TRACE_DELAY_WCF_INSTRUMENTATION_ENABLED
configuration that
enables the updated WCF instrumentation that delays execution until later in
the WCF pipeline when the WCF server exception handling is established. - Add
SIGNALFX_TRACE_HEADER_TAGS
configuration that sets a map of header keys
to tag names. - Add
SIGNALFX_TRACE_KAFKA_CREATE_CONSUMER_SCOPE_ENABLED
configuration that
closes consumer scope on method enter, and starts a new one on method exit. - Add
SIGNALFX_TRACE_LOG_DIRECTORY
configuration that sets directory for logs
and overrides the value inSIGNALFX_TRACE_LOG_PATH
if present. - Add
SIGNALFX_TRACE_LOGGING_RATE
configuration that sets the number of seconds
between identical log messages for tracer log files. - Add
SIGNALFX_TRACE_PARTIAL_FLUSH_ENABLED
configuration that enables partial
flush of traces. - Add
SIGNALFX_TRACE_PARTIAL_FLUSH_MIN_SPANS
configuration that sets the minimum
number of closed spans in a trace before it's partially flushed. - Add
SIGNALFX_VERSION
configuration that sets the application's version that
will populate theversion
tag on spans. - Add
SIGNALFX_TRACE_STARTUP_LOGS
configuration that enables diagnostic log
at startup. - Add
SIGNALFX_TRACE_{0}_ENABLED
configuration pattern that enables/disables
specific integration. - Add
SIGNALFX_TRACE_HTTP_CLIENT_EXCLUDED_URL_SUBSTRINGS
configuration that
sets URLs skipped by the tracer. - Add
SIGNALFX_AZURE_APP_SERVICES
configuration that indicates the profiler
is running in the context of Azure App Services. SIGNALFX_ENDPOINT_URL
now defaults tohttp://localhost:9411/api/v2/spans
.
v0.1.16
v0.1.15
v0.1.14
v0.1.13
Changes:
- Use OpenTelemetry semantic conventions for log correlation
- Remove spans for Confluent.Kafka Consume calls that didn't receive a message
- Add configuration setting,
SIGNALFX_OUTBOUND_HTTP_EXCLUDED_HOSTS
, that prevents the creation of outbound HTTP spans for certain hosts - Added Server-Timing header to ASP.NET on IIS