previews: Add attribute to spans so they can be filtered in Honeycomb#13213
Merged
Conversation
Signed-off-by: ArthurSens <arthursens2005@gmail.com>
vulkoingim
approved these changes
Sep 22, 2022
Contributor
Author
|
Properly tested 🙂 |
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
3 participants
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
Following up from gitpod-io/observability#323, this PR adds an attribute to traces that are emitted by Gitpod in preview environments. This is being done so engineers can filter spans in Honeycomb that are specific for the preview environment they're working on.
Related Issue(s)
Fixes #
How to test
preview.name = <your preview name>Release Notes
Documentation
Werft options:
If enabled this will build
install/previewValid options are
all,workspace,webapp,ide