Operator Documentation Update for SQL Server #29216
Conversation
…Es (#28830) Co-authored-by: joepeeples <joe.peeples@datadoghq.com>
* Clarify tag extraction docs * Fix linter * Update content/en/cloud_cost_management/container_cost_allocation.md Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com> * Move inside the tabs --------- Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
* add note * update all instances * update text * add advanced configuration links * remove go files
* 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.
Co-authored-by: renteria1010 <111309302+renteria1010@users.noreply.github.com>
Co-authored-by: buraizu <bryce.eadie@datadoghq.com>
* Fix link to resource-based sampling guide * Update content/en/tracing/trace_pipeline/ingestion_mechanisms.md --------- Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: estherk15 <esther.kim@datadoghq.com>
Co-authored-by: mabdinur <munir.abdinur@datadoghq.com>
Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
There was an unexpected error while creating the working branch: cannot create branch DataDog/documentation/merge_request:{repository:{owner:"DataDog" name:"documentation"} queued_at:{seconds:1747673154 nanos:773316000} status_with_reason:STATUS_WITH_REASON_QUEUED priority:200 created_at:{seconds:1747673154 nanos:773734000} pull_request_number:29216 base_branch:"master" head_sha:"97f2b64bef51716a8dec98263b76e70a438184b9" id:"687b8347-9c84-4bff-8414-12e0ed40dbf4" status:STATUS_QUEUED triggered_by:"deforest.richards@datadoghq.com" merge_status_workflow_id:"f4480064-3f5a-495d-9e38-b371d55f9bf8_41"} name:"mq-working-branch-master-c3dad5d" temporal_execution_workflow_id:"34a48d0a-7371-4413-9911-c36b1613f657_144" temporal_execution_run_id:"349e26cf-7561-48c3-9642-0214e63b97ff" This could indicate that something doesn't work properly with the build system or that this one has reached its maximum capacity. DetailsError: cannot create branch DataDog/documentation/merge_request:{repository:{owner:"DataDog" name:"documentation"} queued_at:{seconds:1747673154 nanos:773316000} status_with_reason:STATUS_WITH_REASON_QUEUED priority:200 created_at:{seconds:1747673154 nanos:773734000} pull_request_number:29216 base_branch:"master" head_sha:"97f2b64bef51716a8dec98263b76e70a438184b9" id:"687b8347-9c84-4bff-8414-12e0ed40dbf4" status:STATUS_QUEUED triggered_by:"deforest.richards@datadoghq.com" merge_status_workflow_id:"f4480064-3f5a-495d-9e38-b371d55f9bf8_41"} name:"mq-working-branch-master-c3dad5d" temporal_execution_workflow_id:"34a48d0a-7371-4413-9911-c36b1613f657_144" temporal_execution_run_id:"349e26cf-7561-48c3-9642-0214e63b97ff" FullStacktrace: |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do? What is the motivation?
This PR is meant to update our Kubernetes Documentation to include instructions for the Datadog Operator. It also updates a couple configurations to provide more up to date examples. The motivation comes from This Card.
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