-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Added new page for automated analysis, as well as screenshots #29406
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
Conversation
Preview links (active after the
|
Created DOCS-10940 for editorial review 🙂 |
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.
Looking good--thanks for the draft! Let me know if you have any questions about my suggestions. Please feel free to disagree with any of them. 🙂
@@ -0,0 +1,114 @@ | |||
--- | |||
title: Automated Analysis |
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.
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.
I've pushed for that in the past but many of these insights are missing a vital piece to make then a Recommendation which is: always having a clear impact statement.
We can say that the findings here can help with a given issue, but it's hard to definitely tie that to an impact (example: fixing GC issues will reduce CPU load but we can't concretely say by how much due to many other factors). However, when we do have that info, we promote that insight and it will show up in APM recommendations
52e68f3
to
1ec19bb
Compare
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]>
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]>
Co-authored-by: Brett Blue <[email protected]>
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.
Note I switched to use a normal markdown table. Happy to revert if you disagree before we merge. Thanks!
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
What does this PR do? What is the motivation?
This PR is to add documentation for our new feature: Automated Analysis. This includes general explanations, where to find the analysis, as well as a list of current insights.
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