Add otel wrapper #118
Open
Add otel wrapper #118
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 was referenced Sep 26, 2024
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 is designed to lay the groundwork for enabling all build jobs to enable telemetry when they are ready. It works by wrapping commands in a way that runs the command with opentelemetry-instrument, which enables the no-code monkeypatching stuff to take effect.
https://github.com/rapidsai/gha-tools/compare/main...msarahan:gha-tools:add-otel-wrapper?expand=1#diff-f1f054b2906bfd36ad706ed2fa6aa028fa529e65b25167e4ca7ca45546d59ed8R33
The functionality of this PR is ideally non-invasive, because it only becomes active when a particular executable, otel-cli, is available.
Jobs that wish to capture telemetry should:
RAPIDS_SERVICE_NAMEto the desired descriptor of the job running this command (perhaps the job name including build matrix?). This is used as the "service name" in telemetry records.RAPIDS_OTEL_ATTRSto a comma-separated key-value string. These attrs are filterable and are intended for use in later aggregating data. The build scripts should set their own attrs, but if there are additional identifying attributes you want to filter on, you can set them here.These really only apply to the conda builds, because wheel build scripts are more per-repo. Hopefully the wrapper script can serve in those areas.