Emilian Losneanu

1. I see builds fail with p5 because of an issue similar to this 1. our pattern is to start several processes with 1. `dotnet tool restore` 1. then `dotnet...

I can see the same issue. I'm using a brew formula

@heyams can you provide an example where SQL dependency get sampled if duration > 50 ms? So two parts for this problem 1. the duration attribute 3. the logic to...

So, the equivalent in 2.x would be something like ``` public class SqlDependencyFilterProcessor implements TelemetryProcessor { private final TelemetryProcessor next; private final SqlDependencyFilterOptions options; public SqlDependencyFilterProcessor(TelemetryProcessor next, SqlDependencyFilterOptions options) {...

A bit more context: 1. Sometimes we have batch jobs. What we noticed is that the extra dependency calls adds about 150 $ in cost for each hour of batch....

@heyams thanks for your swift answer, I will try today your suggestion for [data collection rules](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-collection-rule-overview). I hope this solution solves the cost problem -- batches introduces anomalies in cost...

@heyams I did an evaluation for adding a rule, but I don't see how I can configure a rule to apply to data to be sent to an appinsights instance,...

@heyams sorry for not responding earlier. We felt like we can't make this work in a straight-forward way, and downgrading to 2.x wasn't the right call, as we already had...

@heyams we did not invest more time into making DCR work either, because it seems too heavy for us. We would need to provision these rules at subscription level, while...

The scenario is the same as the initial description. > I'd like to drop sql dependency spans that are duration is under than a certain threshold. In 2.x and dotnet...