-
Notifications
You must be signed in to change notification settings - Fork 610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Update Configure the client and span profiles doc #3028
[DOC] Update Configure the client and span profiles doc #3028
Conversation
2. Optional: Choose any tags to use in the query. If left blank, the default values of service.name and service.namespace are used. | ||
|
||
The tags you configure must be present in the spans attributes or resources for a trace to profiles span link to appear. You can optionally configure a new name for the tag. This is useful for example if the tag has dots in the name and the target data source doesn’t allow using dots in labels. In that case you can for example remap service.name to service_name. | ||
## View the span profiles in Grafana or Grafana Cloud | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have the full content for Traces to profiles in the Pyroscope documentation. I removed the content from the Traces to profiles and linked to the page instead.
Doc is here: https://grafana.com/docs/pyroscope/next/view-and-analyze-profile-data/profile-tracing/traces-to-profiles/
We can make it live. It's currently in /next. Not sure why it isn't live.
@@ -7,38 +7,52 @@ weight: 100 | |||
|
|||
# Span profiles with Traces to profiles for Go | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The blog post about span profiles has some great content, so I used a few of the paragraphs for the introduction and linked to the blog post.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@kolesnikovae Thank you for the review! Should the wording for your comment above be application-wide or system-wide? |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3028-to-release/v1.4 origin/release/v1.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 87423e4c3f2c7a21323d8e9290220c382350c5fb When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3028-to-release/v1.4
# Create the PR body template
PR_BODY=$(gh pr view 3028 --json body --template 'Backport 87423e4c3f2c7a21323d8e9290220c382350c5fb from #3028{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release/v1.4] [DOC] Update Configure the client and span profiles doc" --body-file - --label "type/docs" --label "backport" --base release/v1.4 --milestone release/v1.4 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3028-to-release/v1.4
# Create a pull request where the `base` branch is `release/v1.4` and the `compare`/`head` branch is `backport-3028-to-release/v1.4`.
# Remove the local backport branch
git switch main
git branch -D backport-3028-to-release/v1.4 |
* Update Configure the client page * Update Span Profiles doc * Apply suggestions from code review * fix broken link from validator * Update _index.md * Update docs/sources/configure-client/go-span-profiles.md (cherry picked from commit 87423e4)
This PR does two things:
Fixes #2771