-
Notifications
You must be signed in to change notification settings - Fork 608
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] Add traces to profile content #2980
[DOC] Add traces to profile content #2980
Conversation
Pyroscope offers both a Command Line Interface (CLI) and an Application Programming Interface (API) to interact with and retrieve profiling data. These tools provide flexibility in how you access and manage your profiling information. | ||
|
||
You can export profiling data from Pyroscope in various formats: | ||
- **JSON**: JSON object easy to integrate with other tools and scripts |
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 most popular is pprof and we support that, to be precised it gzip compressed pprof foo.pprof.gz
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.
Added pprof and removed dot.
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
docs/sources/view-and-analyze-profile-data/profile-tracing/traces-to-profiles.md
Outdated
Show resolved
Hide resolved
Note that there is a link to a page that is created in #2982. The doc validator won't pass because of this broken link (until the other PR is merged). |
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-2980-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 2988c4329f2bac5348e8eccb22f55d53da9d7d75 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-2980-to-release/v1.4
# Create the PR body template
PR_BODY=$(gh pr view 2980 --json body --template 'Backport 2988c4329f2bac5348e8eccb22f55d53da9d7d75 from #2980{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release/v1.4] [DOC] Add traces to profile content" --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-2980-to-release/v1.4
# Create a pull request where the `base` branch is `release/v1.4` and the `compare`/`head` branch is `backport-2980-to-release/v1.4`.
# Remove the local backport branch
git switch main
git branch -D backport-2980-to-release/v1.4 |
* Add traces to profile content * Rename folder to view and analyze * Fix links * Update docs/sources/view-and-analyze-profile-data/_index.md * Apply suggestions from code review * Fix links * Apply suggestions from code review * Update docs/sources/view-and-analyze-profile-data/_index.md * Add link to PR 2982 content * Apply suggestions from code review (cherry picked from commit 2988c43)
* [DOC] Add traces to profile content (#2980) * Add traces to profile content * Rename folder to view and analyze * Fix links * Update docs/sources/view-and-analyze-profile-data/_index.md * Apply suggestions from code review * Fix links * Apply suggestions from code review * Update docs/sources/view-and-analyze-profile-data/_index.md * Add link to PR 2982 content * Apply suggestions from code review (cherry picked from commit 2988c43) * Update docs/sources/configure-server/about-server-api.md
Adds traces to profiles content from Grafana OSS and restructures the invest and analyze profile pages.
This is the updated table of contents with the traces to profiles content:
Fixes #2662