Custom Agents Insights Module Instrumentation #14030
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
antonpirker
changed the title
Bundle ReportChanges will decrease total bundle size by 1.13MB (-5.33%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
Files in
App Routes Affected:
view changes for bundle: sentry-docs-edge-server-array-pushAssets Changed:
Files in
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
This PR adds docs for the new event class API that allows get/set its fingerprint. Corresponding changes were introduced to Unreal SDK in scope of getsentry/sentry-unreal#920. Closes #13733 --------- Co-authored-by: Shannon Anahata <[email protected]>
fix typo
Co-authored-by: openapi-getsentry-bot <[email protected]>
Co-authored-by: Cursor Agent <[email protected]>
Adds an example to better visualise the behaviour of the deep wildcard selector (`**`) if used in a sub-path. closes RELAY-15
Closes getsentry/sentry-dart#2782 Should only be merged once Flutter v9 is GA
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR Adds docs for Flutter Feature Flag implementation, which will be available in the upcoming v9 release. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## EXTRA RESOURCES - [ [Flutter] Feature Flags Reporting](getsentry/sentry-dart#2746) --------- Co-authored-by: Giancarlo Buenaflor <[email protected]> Co-authored-by: Michelle Zhang <[email protected]>
Closes getsentry/sentry-dart#2702 Do not merge until Flutter v9 is GA --------- Co-authored-by: Alex Krawiec <[email protected]> Co-authored-by: Giancarlo Buenaflor <[email protected]>
…#13982) Makes it clearer how to set up to get additional data such as network details and how to use it with third party widgets --------- Co-authored-by: Jasmin <[email protected]>
ref convos in getsentry/relay#4689 The `attributes` section in `develop-docs/sdk/telemetry/logs.mdx` was updated to clarify handling of 64-bit unsigned integers. * Initially, the text "In the future we will support 64-bit unsigned integers." was replaced with "For 64-bit unsigned integers, use the `string` type to avoid overflow issues." * This change was made to provide immediate guidance based on internal discussions, recommending `string` conversion to prevent data loss or precision issues. * Subsequently, the documentation was further refined to include both the current guidance and the future roadmap. * The line now reads: "For 64-bit unsigned integers, use the `string` type to avoid overflow issues. In the future we will support 64-bit unsigned integers." * This ensures SDK developers and third-party integration authors have clear instructions for current implementation while also being aware of planned native support. --------- Co-authored-by: Cursor Agent <[email protected]>
…ns (#13943) adds documentation for new options available in `browserTracingIntegration`: - `ignorePerformanceApiSpans` - `ignoreResourceSpans` - `onRequestSpanStart` (this has been around for some time but we never documented it, oops) Furthermore, I decided to give this page a little face lift by using the `<SdkOption>` component for a unified appearance of options. This also included adding a table row for "Available Since" to the `<SdkOption>` component, since a lot of these option descriptions previously used texts or alerts to specify the min SDK version. Also made some minor adjustments to outdated documentation on related pages.
Co-authored-by: openapi-getsentry-bot <[email protected]>
Documentation for .NET profiling support was updated to reflect compatibility with .NET 8.0+ only, addressing observed compilation issues on .NET 6.0. Specific changes include: * In `docs/platforms/dotnet/common/profiling/index.mdx`, the alert message was updated to state profiling is "available in _Alpha_ on .NET 8.0+". * `docs/platforms/dotnet/common/profiling/troubleshooting/index.mdx` now specifies support for ".NET 8.0+" instead of ".NET 6.0, .NET 7.0 and .NET 8.0". * The profiling onboarding alert in `docs/platforms/dotnet/index.mdx` was changed to "available in Alpha on .NET 8.0 and newer". * The JSON alert message in `public/_platforms/dotnet/profiling-onboarding-0-alert.json` was updated from "for .NET 6.0+" to "for .NET 8.0+". These updates ensure the documentation accurately reflects the required .NET version for profiling, preventing future compatibility issues. Co-authored-by: Cursor Agent <[email protected]>
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> [Latest Vercel Preview](https://sentry-docs-git-joshua-nativebeforesenddocs.sentry.dev/platforms/native/configuration/filtering/#event-hints) ## DESCRIBE YOUR PR Fixes getsentry/sentry-native#1268 We fix some ancient docs which wrongly state that `before_send` uses the `hint` parameter in the Native SDK, by cleaning up the unnecessary 'Event Hints' section. We move the example snippet into the corresponding `before_send` and `on_crash` sections, better showcasing how to use the passed-in values. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
This PR moves the detailed description of all Sentry Unreal Engine SDK installation options to a dedicated `Installation Methods` page. This simplifies the landing page and lets us clearly highlight the recommended installation method which is downloading the SDK from the GitHub Releases page.
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR Adds documentation for Native SDK PR - getsentry/sentry-native#1266 > Platforms / Native / Enriching Events / Attachments ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [x] Checked Vercel preview for correctness, including links - [x] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
## DESCRIBE YOUR PR We're updating Seer's default settings in Sentry. This updates the docs to reflect that change. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [x] Urgent deadline (GA date, etc.): 6/20 - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Shannon Anahata <[email protected]>
…#14118) Was using these docs and noticed the outdated usages of `yarn`. Updated to use the working `pnpm` usages
## DESCRIBE YOUR PR For the Sentry Prevent AI beta releasing in June ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Shannon Anahata <[email protected]>
Markdown table formatting was corrected in `platform-includes/configuration/integrations/javascript.nestjs.mdx`. The changes addressed rendering issues caused by misaligned columns and extra pipe characters. Specifically: * The table header separator row was adjusted by removing an extraneous `| --- |` to align with a 5-column structure. * The `supabaseIntegration` row was modified to remove an extra, empty column. * The checkmark in the `unleashIntegration` row was relocated to the correct "Additional Context" column, resolving its placement in an unintended extra column. These adjustments ensure the table consistently renders with five columns: "Integration name", "Auto Enabled", "Errors", "Tracing", and "Additional Context", improving readability and visual alignment. Co-authored-by: Cursor Agent <[email protected]>
There is no `Hub` anymore, it was deprecated in 2.0. Direct link to preview: https://sentry-docs-git-ivana-pythonupdate-draining-page.sentry.dev/platforms/python/configuration/draining/ ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [x] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Alex Krawiec <[email protected]>
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR *Tell us what you're changing and why. If your PR **resolves an issue**, please link it so it closes automatically.* ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Lorenzo Cian <[email protected]>
…14087) ## DESCRIBE YOUR PR EnableInExpoDevelopment looks like it disable sentry on non dev envs. `__DEV__` is under prod = false which would mean Sentry = disabled or? ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
Contributor
Author
|
closing in favor of #14133 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Documentation how to manually instrument your AI Agent so the data shows up in the new "Agents Insights Module".
Preview:
https://sentry-docs-git-antonpirker-agents-module-custom-instrumenation.sentry.dev/python/tracing/instrumentation/custom-instrumentation/agents-module/#common-span-attributes
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES