-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Conversation
Preview links (active after the
|
dc7b94d
to
73fb158
Compare
bd50623
to
8074288
Compare
7487af9
to
40b633a
Compare
40b633a
to
acf429c
Compare
8456553
to
0bcb054
Compare
Co-authored-by: meghanlo <[email protected]>
Co-authored-by: meghanlo <[email protected]>
0bcb054
to
f712398
Compare
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.
This looks great! I added some minor writing suggestions - let me know if you have any questions 🙂
return MultiTransport | ||
{{< /code-block >}} | ||
|
||
- Use as follows: |
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.
- 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?
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! |
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.
All set :)
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
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:
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