feat(core): Make sure Supabase db query insights are populated #16169
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
DB must be set to populate query/database insights
|
@onurtemizkan this is to ensure that the db query insights is populated, the logic is not quite right in the product IMO. But setting only db for the span op is fine and the sentry.op will have db.{crud-op} I just investigated this with cursor. Could you take over this PR to make sure it is correct, please? Develop docs are a bit wrong |
onurtemizkan
approved these changes
May 2, 2025
onurtemizkan
changed the title
AbhiPrasad
approved these changes
May 28, 2025
AbhiPrasad
approved these changes
May 28, 2025
This was referenced Sep 29, 2025
This was referenced Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
DB must be set to populate query/database insights