Supported technologiesedit
If your favorite technology is not supported yet, you can vote for it by participating in our survey. We will use the results to add support for the most requested technologies.
Another option is to add a dependency to the agent’s public API in order to programmatically create custom transactions and spans.
If you want to extend the auto-instrumentation capabilities of the agent, the contributing guide should get you started.
If, for example, the HTTP client library of your choice is not listed, it means that there won’t be spans for those outgoing HTTP requests. If the web framework you are using is not supported, the agent will not capture transactions.
.NET versionsedit
The agent works on every .NET flavor and version that supports .NET Standard 2.0. This means .NET Core 2.0 (or newer) and .NET Framework 4.6.1 (or newer).
Web frameworksedit
Automatic instrumentation for a web framework means a transaction is automatically created for each incoming request and it is named after the registered route.
We support automatic instrumentation for the following web frameworks.
| Framework | Supported versions | Supported since agent’s version |
|---|---|---|
ASP.NET Core |
2.1 and later |
1.0 |
ASP.NET (.NET Framework) on IIS |
4.6.1 or newer (IIS 7.0 or newer) |
1.1 |
RPC Frameworksedit
The agent supports gRPC on .NET Core both on the client and the server side. Every gRPC call is automatically captured by the agent.
Streaming is not supported. In practice this means for streaming use-cases the agent does not create transactions and spans automatically.
| Framework | Supported versions | Supported since agent’s version |
|---|---|---|
gRPC on .NET Core |
2.23.2 and later |
1.7 |
Data access technologiesedit
We support automatic instrumentation for the following data access technologies.
| Data access technology | Supported versions | Notes | Supported since agent’s version |
|---|---|---|---|
Entity Framework (EF) Core |
2.x |
A DB span is automatically created for each access to underlying database performed by Entity Framework Core. |
1.0 |
Entity Framework (EF) 6 |
6.2 and later |
A DB span is automatically created for each access to underlying database performed by Entity Framework 6. |
1.2 |
Elasticsearch (Elasticsearch.Net and NEST) |
7.6.0 |
If you’re using 7.10.1 or 7.11.0, upgrade to at least 7.11.1 which fixes a bug in capture |
1.6.0 |
Redis (StackExchange.Redis) |
2.0.495 |
A DB span is automatically created for each profiled redis command peformed by StackExchange.Redis |
1.8.0 |
Networking client-side technologiesedit
Automatic instrumentation for networking client-side technology means
an HTTP span is automatically created for each outgoing HTTP request and tracing headers are propagated.
The spans are named after the schema <method> <host>, for example GET elastic.co.
| Framework | Supported versions | Supported since agent’s version |
|---|---|---|
System.Net.Http.HttpClient on .NET Core |
1.0 |
|
System.Net.Http.HttpClient on .NET Framework |
1.1 |