We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As span data is set today, it will not appear in Sentry's Query Module.
Span's must be set in the required format to display in the query module.
We should comply as much as possible from a client side PoV but it may also be reasonable to add db.supabase similar to db.prisma
db.supabase
db.prisma
Specifically Operation should be
db.sql.query
db.system: postgresql
The text was updated successfully, but these errors were encountered:
in the case of Prism in relay, Sentry accepts a special case
from Kamil
For supabase there is no raw SQL query, so they use https://postgrest.org/en/v12/index.html
Sorry, something went wrong.
@kamilogorek what kind of cardinality should we expect with PostgREST
Is it parameterized by nature or within the integration in anyway?
@kamilogorek fyi getsentry/relay#3153
@smeubank following up on this, it looks like there's no changes required now on the integration side?
No branches or pull requests
Feature request
As span data is set today, it will not appear in Sentry's Query Module.
Describe the solution you'd like
Span's must be set in the required format to display in the query module.
Describe alternatives you've considered
We should comply as much as possible from a client side PoV but it may also be reasonable to add
db.supabase
similar todb.prisma
Additional context
Specifically Operation should be
db.sql.query
or other from listdb.system: postgresql
The text was updated successfully, but these errors were encountered: