We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The version of the Elastic.Apm nuget package used: 1.28.3
Elastic.Apm
1.28.3
After #2418 it's not possible to add custom filters anymore.
_allowFilterAdd is never set to true. It seems the only active filters are predefined filters added via internal SetUpFilters method.
_allowFilterAdd
true
SetUpFilters
apm-agent-dotnet/src/Elastic.Apm/Report/PayloadSenderV2.cs
Line 151 in eae543f
Call Agent.AddFilter method after Agent was initialized and expect true as return value .
Call Agent.AddFilter method before Agent gets initialized and expect the filter to be present in the filters list after Agent initialization.
The text was updated successfully, but these errors were encountered:
Fix #2421 ensure _allowFilterAdd is true on initialization
84bdfce
b2621c8
Successfully merging a pull request may close this issue.
APM Agent version
The version of the
Elastic.Apmnuget package used:1.28.3Describe the bug
After #2418 it's not possible to add custom filters anymore.
_allowFilterAddis never set totrue. It seems the only active filters are predefined filters added via internalSetUpFiltersmethod.apm-agent-dotnet/src/Elastic.Apm/Report/PayloadSenderV2.cs
Line 151 in eae543f
To Reproduce
Call Agent.AddFilter method after Agent was initialized and expect
trueas return value .Call Agent.AddFilter method before Agent gets initialized and expect the filter to be present in the filters list after Agent initialization.
The text was updated successfully, but these errors were encountered: