Update Continuous Profiler source code instructions #31721
Merged
Conversation
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
github-actions
bot
added
Images
PyvesB
commented
Sep 18, 2025
Comment on lines
-488
to
-494
| You can also see links from profile frames to their source repository. This is supported for profiles broken down by line, method, or file. | ||
|
|
||
| 1. Navigate to [**APM** > **Profile Search**][2]. | ||
| 2. Hover your cursor over a method in the flame graph. A kebab icon with the **More actions** label appears on the right. | ||
| 3. Click **More actions** > **View in repo** to open the trace in its source code repository. | ||
|
|
||
| {{< img src="integrations/guide/source_code_integration/profiler-link-to-git.png" alt="Link to GitHub from the Continuous Profiler" style="width:100%;">}} |
There was a problem hiding this comment.
The View in repo flow is technically still supported at the time of writing. Rather than overwhelming users with all the ways they can achieve the same goal, I chose to be opinionated and only advertise one.
Preview links (active after the
|
wincent
reviewed
Sep 19, 2025
Comment on lines
-488
to
-494
| You can also see links from profile frames to their source repository. This is supported for profiles broken down by line, method, or file. | ||
|
|
||
| 1. Navigate to [**APM** > **Profile Search**][2]. | ||
| 2. Hover your cursor over a method in the flame graph. A kebab icon with the **More actions** label appears on the right. | ||
| 3. Click **More actions** > **View in repo** to open the trace in its source code repository. | ||
|
|
||
| {{< img src="integrations/guide/source_code_integration/profiler-link-to-git.png" alt="Link to GitHub from the Continuous Profiler" style="width:100%;">}} |
brett0000FF
approved these changes
Sep 19, 2025
Co-authored-by: Brett Blue <[email protected]>
Co-authored-by: Brett Blue <[email protected]>
Co-authored-by: Brett Blue <[email protected]>
Co-authored-by: Brett Blue <[email protected]>
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.
What does this PR do? What is the motivation?
The screenshot and instructions to view source code in the Continuous Profiler were outdated, let's update them!
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes