Caution
The SignalFx Instrumentation for .NET is deprecated as of February 21, 2024 and will reach End of Support on February 21 2025. Until then, only critical security fixes and bug fixes will be provided. After the date, the library will be archived and no longer maintained.
New customers instrumenting the .NET ecosystem should use the Splunk Distribution of OpenTelemetry .NET. Existing customers should consider migrating to Splunk Distribution of OpenTelemetry .NET which offers similar capabilities. To learn how to migrate, see Migrate from the SignalFx .NET Instrumentation.
SignalFx Instrumentation for .NET (Deprecated) 🔗
The SignalFx Instrumentation for .NET provides zero-code instrumentation for popular .NET libraries and frameworks to collect and send telemetry data to Splunk Observability Cloud.
The SignalFx Instrumentation for .NET provides the following features:
Collection and reporting of all spans
AlwaysOn Profiling for CPU and memory
Database Query Performance (from version 1.4.0)
B3 and W3C headers for context propagation
Zipkin trace exporter to send spans as JSON
Support for existing custom instrumentation through OpenTracing
Semantic conventions inspired by the OpenTelemetry standards
To instrument your .NET application, follow these steps:
Check compatibility and requirements. See .NET instrumentation compatibility and requirements.
Instrument your .NET application. See .NET application for Splunk Observability Cloud.
Configure your instrumentation. See Configure the SignalFx Instrumentation for .NET.
You can also automatically instrument your .NET applications along with the Splunk Distribution of OpenTelemetry Collector installation. Zero-code instrumentation removes the need to install and configure the .NET library separately. See Automatic discovery for back-end applications in Windows for the installation instructions.