Skip to content
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

DOCS-10359: kubernetes cpu usage faq #28199

Merged
merged 2 commits into from
Mar 20, 2025

Conversation

cswatt
Copy link
Contributor

@cswatt cswatt commented Mar 17, 2025

What does this PR do? What is the motivation?

Customer requested more information about difference between kubernetes.cpu.* and container.cpu.* metrics. Adding a link to a new FAQ page about these metrics and how/why they are different.

Merge instructions

Merge readiness:

  • Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

@cswatt cswatt added the WORK IN PROGRESS No review needed, it's a wip ;) label Mar 17, 2025
@cswatt cswatt requested a review from a team as a code owner March 17, 2025 19:19
@github-actions github-actions bot added the FAQ Content impacting a FAQ label Mar 17, 2025
@cswatt cswatt removed the WORK IN PROGRESS No review needed, it's a wip ;) label Mar 17, 2025
Copy link
Contributor

@brett0000FF brett0000FF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@cswatt
Copy link
Contributor Author

cswatt commented Mar 18, 2025

/merge

@dd-devflow
Copy link

dd-devflow bot commented Mar 18, 2025

View all feedbacks in Devflow UI.
2025-03-18 17:12:54 UTC ℹ️ Start processing command /merge


2025-03-18 17:13:01 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 9m (p90).


2025-03-18 17:13:24 UTC 🚨 MergeQueue: This merge request is in error

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:1742317978 nanos:629704000} status_with_reason:STATUS_WITH_REASON_QUEUED priority:200 created_at:{seconds:1742317978 nanos:630069000} pull_request_number:28199 base_branch:"master" head_sha:"cd6905b2a9f3d70fa0418288ff803e8a13031258" id:"822f1f1f-d6f0-4ccf-96ba-561cd3e19a13" status:STATUS_QUEUED triggered_by:"[email protected]" merge_status_workflow_id:"dcf2748e-78ba-4094-ab09-62fa38d83447_41"} name:"mq-working-branch-master-744173d" temporal_execution_workflow_id:"4aa71ca7-7c99-402b-911d-1892ba49d9c4_131" temporal_execution_run_id:"9b091bda-2ce0-4e83-afc4-5fca34be050b"

This could indicate that something doesn't work properly with the build system or that this one has reached its maximum capacity.
You can try to wait a bit and then re-add your pull request to the queue!

Details

Error: cannot create branch DataDog/documentation/merge_request:{repository:{owner:"DataDog" name:"documentation"} queued_at:{seconds:1742317978 nanos:629704000} status_with_reason:STATUS_WITH_REASON_QUEUED priority:200 created_at:{seconds:1742317978 nanos:630069000} pull_request_number:28199 base_branch:"master" head_sha:"cd6905b2a9f3d70fa0418288ff803e8a13031258" id:"822f1f1f-d6f0-4ccf-96ba-561cd3e19a13" status:STATUS_QUEUED triggered_by:"[email protected]" merge_status_workflow_id:"dcf2748e-78ba-4094-ab09-62fa38d83447_41"} name:"mq-working-branch-master-744173d" temporal_execution_workflow_id:"4aa71ca7-7c99-402b-911d-1892ba49d9c4_131" temporal_execution_run_id:"9b091bda-2ce0-4e83-afc4-5fca34be050b"

FullStacktrace:
child workflow execution error (type: mergequeue_private.MergeQueue_BuildWorkingBranch, workflowID: 4aa71ca7-7c99-402b-911d-1892ba49d9c4_131, runID: 9b091bda-2ce0-4e83-afc4-5fca34be050b, initiatedEventID: 131, startedEventID: 132): cannot create branch DataDog/documentation/merge_request:{repository:{owner:"DataDog" name:"documentation"} queued_at:{seconds:1742317978 nanos:629704000} status_with_reason:STATUS_WITH_REASON_QUEUED priority:200 created_at:{seconds:1742317978 nanos:630069000} pull_request_number:28199 base_branch:"master" head_sha:"cd6905b2a9f3d70fa0418288ff803e8a13031258" id:"822f1f1f-d6f0-4ccf-96ba-561cd3e19a13" status:STATUS_QUEUED triggered_by:"[email protected]" merge_status_workflow_id:"dcf2748e-78ba-4094-ab09-62fa38d83447_41"} name:"mq-working-branch-master-744173d" temporal_execution_workflow_id:"4aa71ca7-7c99-402b-911d-1892ba49d9c4_131" temporal_execution_run_id:"9b091bda-2ce0-4e83-afc4-5fca34be050b" (type: MergeQueueError, retryable: false): activity error (type: github.GithubService_CreateRefFromSha, scheduledEventID: 20, startedEventID: 21, identity: 1@github-worker-5844b9f7bf-qbg2c@): cannot create new ref using the github API: PATCH https://api.github.com/repos/DataDog/documentation/git/refs/heads/mq-working-branch-master-744173d: 422 Reference does not exist [] (type: GitUnprocessableEntity, retryable: false): PATCH https://api.github.com/repos/DataDog/documentation/git/refs/heads/mq-working-branch-master-744173d: 422 Reference does not exist [] (type: ErrorResponse, retryable: true)

@cswatt
Copy link
Contributor Author

cswatt commented Mar 20, 2025

/merge

@dd-devflow
Copy link

dd-devflow bot commented Mar 20, 2025

View all feedbacks in Devflow UI.
2025-03-20 22:26:20 UTC ℹ️ Start processing command /merge


2025-03-20 22:26:25 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 9m (p90).


2025-03-20 22:32:08 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit 01b8af3 into master Mar 20, 2025
14 of 17 checks passed
@dd-mergequeue dd-mergequeue bot deleted the cswatt/docs-10359-cpu-usage-metric branch March 20, 2025 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FAQ Content impacting a FAQ mergequeue-status: done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants