adding scrape protocol and ID for prometheus receiver #211
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
sethAmazon
previously approved these changes
May 3, 2024
sethAmazon
approved these changes
May 3, 2024
musa-asad
approved these changes
May 3, 2024
sethAmazon
merged commit cc2b921
into
amazon-contributing:aws-cwa-dev
104 of 110 checks passed
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.
Description:
scrapeProtocalsconfig for DCGM prometheus scraperWith a recent change to prometheus receiver, we need to pass IDs to create a multiple instances of prometheus receivers within the same process (eg. aws CI receiver).
Related ticket: open-telemetry#32123
Testing:
Validated with a test cluster that contains both Tranium and NVIDIA instances
Documentation: