feat: Filter platform metadata at the source - #911
Merged
Conversation
Add utilities functions to normalize platform metadata names into lowercase ASCII identifiers and build source-to-normalized mappings.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #911 +/- ##
==========================================
+ Coverage 77.22% 80.28% +3.06%
==========================================
Files 83 86 +3
Lines 3144 3176 +32
==========================================
+ Hits 2428 2550 +122
+ Misses 716 626 -90
🚀 New features to boost your workflow:
|
Allow users to expose selected Kubernetes pod labels as normalized report metadata instead of propagating every available label.
…ver metadata Only propagate explicitly selected server metadata instead of adding every available entry to reports.
gfieni
force-pushed
the
feat/filter-metadata-from-source
branch
from
August 20, 2026 12:56
039f243 to
8fe74e9
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
1 participant
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.
This pull request allows users to explicitly select which Kubernetes pod labels and OpenStack server metadata are exposed on reports.
Instead of propagating all available platform metadata and filtering it for each report, metadata is filtered and normalized when synchronizing with the platform API. The selected entries are stored in a flat structure and added to reports through shared metadata registries.
The OpenStack processor also uses incremental server synchronization to avoid performing a full refresh at every polling interval.