Skip to content

Add Error Tracking + Sentry SDK documentation #28778

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

Merged
merged 6 commits into from
Apr 22, 2025

Conversation

milanboers
Copy link
Member

@milanboers milanboers commented Apr 15, 2025

What does this PR do? What is the motivation?

Adds documentation on the Sentry SDK compatibility for Error Tracking / Logs (in Preview).

Merge instructions

Merge readiness:

  • Ready for merge

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:

/merge

Additional notes

Copy link
Contributor

github-actions bot commented Apr 15, 2025

Preview links (active after the build_preview check completes)

New or renamed files

Modified Files

@milanboers milanboers force-pushed the milanboers/sentry-sdk branch 3 times, most recently from dc7b94d to 73fb158 Compare April 15, 2025 12:11
@milanboers milanboers force-pushed the milanboers/sentry-sdk branch 3 times, most recently from bd50623 to 8074288 Compare April 15, 2025 16:18
@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Apr 15, 2025
@milanboers milanboers force-pushed the milanboers/sentry-sdk branch 6 times, most recently from 7487af9 to 40b633a Compare April 15, 2025 18:11
@milanboers milanboers force-pushed the milanboers/sentry-sdk branch from 40b633a to acf429c Compare April 17, 2025 09:31
@github-actions github-actions bot added the Images Images are added/removed with this PR label Apr 17, 2025
@milanboers milanboers force-pushed the milanboers/sentry-sdk branch 10 times, most recently from 8456553 to 0bcb054 Compare April 17, 2025 15:59
@milanboers milanboers marked this pull request as ready for review April 17, 2025 16:02
@milanboers milanboers requested a review from a team as a code owner April 17, 2025 16:02
@milanboers milanboers requested review from iadjivon and meghanlo April 17, 2025 16:02
@milanboers milanboers force-pushed the milanboers/sentry-sdk branch from 0bcb054 to f712398 Compare April 17, 2025 16:05
Copy link
Contributor

@janine-c janine-c left a comment

Choose a reason for hiding this comment

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

This looks great! I added some minor writing suggestions - let me know if you have any questions 🙂

return MultiTransport
{{< /code-block >}}

- Use as follows:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Use as follows:
2. Use as follows:

I find this phrasing a little awkward and vague, and we use it a few times. I'm wondering if there's more context we can give - for example, why these code snippets are separated out and where they should go?

@iadjivon iadjivon self-assigned this Apr 18, 2025
@iadjivon iadjivon added the editorial review Waiting on a more in-depth review label Apr 18, 2025
@github-actions github-actions bot removed the Architecture Everything related to the Doc backend label Apr 21, 2025
@iadjivon
Copy link
Contributor

Hi @milanboers, we reviewed and added this page under the "Guides" section of error tracking.

Let me know if you'd like to add anything else or if it is all set to merge!

Copy link
Contributor

@iadjivon iadjivon left a comment

Choose a reason for hiding this comment

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

All set :)

@iadjivon
Copy link
Contributor

/merge

@dd-devflow
Copy link

dd-devflow bot commented Apr 22, 2025

View all feedbacks in Devflow UI.

2025-04-22 15:48:22 UTC ℹ️ Start processing command /merge


2025-04-22 15:48:26 UTC ℹ️ MergeQueue: pull request added to the queue

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


2025-04-22 16:03:48 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit 122a7b9 into master Apr 22, 2025
17 of 20 checks passed
@dd-mergequeue dd-mergequeue bot deleted the milanboers/sentry-sdk branch April 22, 2025 16:03
@milanboers milanboers mentioned this pull request Apr 22, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial review Waiting on a more in-depth review Images Images are added/removed with this PR mergequeue-status: done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants