-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add Memory Leaks section #28776
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
Add Memory Leaks section #28776
Conversation
Preview links (active after the
|
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.
Left some suggestions to remove temporal words, but looks good! Thanks for adding to the docs!
Co-authored-by: Esther Kim <[email protected]>
Co-authored-by: Esther Kim <[email protected]>
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
* Add Memory Leaks section * Add screenshot to the Memory Leaks section. * Update content/en/tracing/services/service_page.md Co-authored-by: Esther Kim <[email protected]> * Update content/en/tracing/services/service_page.md Co-authored-by: Esther Kim <[email protected]> --------- Co-authored-by: Esther Kim <[email protected]>
What does this PR do? What is the motivation?
Adds a section describing the Memory Leaks section of the service page.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in 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.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes