-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Post Reorg Tweaks #28940
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
Post Reorg Tweaks #28940
Conversation
Preview links (active after the
|
Approved by PMs offline |
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.
Is this also supposed to be an item in the navigation? Asking since Logs and Metrics are listed.
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.
Thanks for the review! No, not yet. This is still supposed to be hidden for now. Thanks for checking though. 😄
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
* Change name of Env Var and OTel API in nav. * Change Direct OTLP Ingest to Agentless Deployment in nav. * Change Direct OTLP Ingest to Agentless Deployment in content. * Add example app + demo under Getting Started. * Tweak wording. * Make wording consistent for Getting Started landing page. * Revert agentless deployment outside of nav and setup page. * Revert change.
* Change name of Env Var and OTel API in nav. * Change Direct OTLP Ingest to Agentless Deployment in nav. * Change Direct OTLP Ingest to Agentless Deployment in content. * Add example app + demo under Getting Started. * Tweak wording. * Make wording consistent for Getting Started landing page. * Revert agentless deployment outside of nav and setup page. * Revert change.
What does this PR do? What is the motivation?
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