-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Teddy.gesbert/doc dora #28914
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
base: master
Are you sure you want to change the base?
Teddy.gesbert/doc dora #28914
Conversation
Co-authored-by: Jorge Calvar <[email protected]>
Change deployment.merge_time to Merge Time (i.e. metric to field) to avoid any confusion with previous Metrics type
…tion into teddy.gesbert/doc-dora
Applied suggestions from Joe Peeples
Co-authored-by: Alicia Scott <[email protected]>
Co-authored-by: Alicia Scott <[email protected]>
- Added consistency between data sources requirements. - Remove /dora_metrics/failures/datadog_incidents alias as not needed.
Co-authored-by: Alicia Scott <[email protected]>
Added backfill documentation for retrieving past incidents using Incident Management as a DORA failure source.
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.
Just a couple of small suggestions! Also, could you fix the merge conflict?
Co-authored-by: May Lee <[email protected]>
Co-authored-by: May Lee <[email protected]>
Preview links (active after the
|
/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
This PR is rejected because it was updated |
What does this PR do? What is the motivation?
Added documentation for backfilling historical data when using Incident Management as a DORA failure source.
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