feat: Add Prometheus gauges for FeatureStore installation telemetry#6354
Open
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
Open
feat: Add Prometheus gauges for FeatureStore installation telemetry#6354ntkathole wants to merge 1 commit intofeast-dev:masterfrom
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
Conversation
ntkathole
force-pushed
the
operator_metrics
branch
from
4640555 to
c547a6e
Compare
ntkathole
force-pushed
the
operator_metrics
branch
4 times, most recently
from
927d4b2 to
cb5f85a
Compare
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
ntkathole
force-pushed
the
operator_metrics
branch
from
cb5f85a to
739711a
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.
What this PR does / why we need it:
Adds a single Prometheus info gauge to the feast-operator that records the
configured store types (online store, offline store, registry) for each
FeatureStoreCR. This gives platform teams visibility into which store typesare deployed across the cluster.
feast_operator_feature_store_info{namespace, name, online_store_type, offline_store_type, registry_type} = 1