feat(telemetry): add runtime EventName filtering for internal logs#3511
Draft
cijothomas wants to merge 7 commits into
Draft
feat(telemetry): add runtime EventName filtering for internal logs#3511cijothomas wants to merge 7 commits into
cijothomas wants to merge 7 commits into
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3511 +/- ##
========================================
Coverage 86.51% 86.52%
========================================
Files 782 783 +1
Lines 313105 313396 +291
========================================
+ Hits 270893 271169 +276
- Misses 41688 41703 +15
Partials 524 524
🚀 New features to boost your workflow:
|
Pull request dashboard statusStatus last refreshed: 2026-07-22 19:57:38 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected. |
cijothomas
force-pushed
the
eventname-filter-spike-rebased
branch
from
July 18, 2026 17:27
0d4ae23 to
a14ccbc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Summary
Adds EventName-level filtering for
df_engineinternal telemetry logs. The newengine.telemetry.logs.eventsconfiguration is combined with the existing level and target filter, and supports mutually exclusive allow and deny lists with exact or trailing-wildcard prefix patterns.The filter reads the OpenTelemetry EventName from
tracing::Metadata::name(). Because the EventName is static for each tracing callsite, the filter caches anInterest::always()orInterest::never()decision instead of evaluating the policy for every event. Policy updates useArcSwapfor atomic replacement and rebuild tracing's callsite interest cache, moving matching cost to configuration updates and keeping it off the emission hot path.Successful full-engine reconciliation applies the validated EventName policy to the shared runtime filter, including configuration received through the OpAMP controller extension. Failed or invalid reconciliation preserves the active filter.
What issue does this PR close?
Relates to #3387
Are there any user-facing changes?
Yes. Users can filter internal telemetry logs by EventName through static configuration or full-engine remote configuration without restarting the engine or rebuilding tracing subscribers.
Changelog
.chloggen/*.yamlentrychore(indicated in title)