scenarios: Add benchmark that uses OTel to scrape all prometheus metrics #11
Conversation
This file contains 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
This change does the following: - Update the load generator manifests so it doesn't define how to collect (PodMonitoring configs defined in the scenarios directly) - Add OTel manifests that run in its own namespace - Add OTel config as a config map directly and run it as a daemonset TODO: - Get this working :( Still seeing no avalance metrics, even though the self metrics are being ingested into GMP - Lose the dependency on the GMP operator when the OTel benchmark is run
ridwanmsharif
force-pushed
the
ridwanmsharif/otel-bench
branch
from
a68a53f to
bfc4b7f
Compare
ridwanmsharif
force-pushed
the
ridwanmsharif/otel-bench
branch
from
bfc4b7f to
ff96f9a
Compare
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.
This change does the following:
TODO: