You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring Sampling, we allow users to set both the Include and Exclude properties.
This is a logical fallacy because this is a binary decision. An item cannot be both included and excluded.
In our current implementation, the Excluded types will always win over the Included types.
(we actually have a test to guarantee this behavior).
Problem
When configuring Sampling, we allow users to set both the Include and Exclude properties.
This is a logical fallacy because this is a binary decision. An item cannot be both included and excluded.
In our current implementation, the Excluded types will always win over the Included types.
(we actually have a test to guarantee this behavior).
Exclude:
ApplicationInsights-dotnet/src/ServerTelemetryChannel/SamplingTelemetryProcessor.cs
Lines 80 to 84 in 981feb7
Include:
ApplicationInsights-dotnet/src/ServerTelemetryChannel/SamplingTelemetryProcessor.cs
Lines 99 to 103 in 981feb7
Evaluation:
ApplicationInsights-dotnet/src/ServerTelemetryChannel/SamplingTelemetryProcessor.cs
Lines 282 to 296 in 981feb7
Test:
ApplicationInsights-dotnet/Test/ServerTelemetryChannel.Test/Shared.Tests/SamplingTelemetryProcessorTest.cs
Lines 327 to 339 in 981feb7
Proposal
I want to simplify our internal types and codify the assumptions we're making in our evaluation method.
includedTypes
The text was updated successfully, but these errors were encountered: