This issue is to add an equivalent to transaction_ignore_urls, and also to make it configurable via central config, dynamically, if possible.
The first option to achieve this is simply to ensure that a Filter is configured on the ASP.NET and ASP.NET Core instrumentation options. In ASP.NET Core instrumentation, for example, we have AspNetCoreTraceInstrumentationOptions which includes this property public Func<HttpContext, bool>? Filter { get; set; }. This can be used by a consumer to filter the requests for which a trace should be captured. ASP.NET (classic) instrumentation also supports options for this.
An alternative option is to consider a rule-based sampler, if this is a better way to support dynamic configuration and/or reliablity.
This issue is to add an equivalent to transaction_ignore_urls, and also to make it configurable via central config, dynamically, if possible.
The first option to achieve this is simply to ensure that a
Filteris configured on the ASP.NET and ASP.NET Core instrumentation options. In ASP.NET Core instrumentation, for example, we have AspNetCoreTraceInstrumentationOptions which includes this property public Func<HttpContext, bool>? Filter { get; set; }. This can be used by a consumer to filter the requests for which a trace should be captured. ASP.NET (classic) instrumentation also supports options for this.An alternative option is to consider a rule-based sampler, if this is a better way to support dynamic configuration and/or reliablity.