QoL SDK API Improvments

[HazAT]

QoL Improvement Idea Collection

• Product / Generic

  • Make trace more prominent in UI, maybe merge with span view on transaction so you can more easily navigate transactions and drill down into spans
  • Put JSON button in the same place for issues and transactions

• Python

  • Decorators for Performance API
    • Instead of with.transactions → @sentry_sdk.instrument
    • Timed decorator: “sample the transaction/span for this function if it’s slower than N seconds” (for people who want to automatically ignore fast/good transactions)
    • Decorators could optionally inject the transaction/span object as a function attribute, so people don’t have to manually get the transaction to e.g. set some attributes or start a child span

• Ruby

  • Magic import instruments functions?

• Go

  • better global Hub / vs local Hub APIs
    • sentry.GetGlobalHub()
    • sentry.WithGlobalScope()
    • …
  • Remove StartSpan, it’s confusing
  • More ways to start transactions
    • StartTransaction(”name”, …options)
    • StartTransactionFromContext(”name”, ctx, …options)
    • See for more inspiration https://docs.datadoghq.com/tracing/trace_collection/custom_instrumentation/go/
  • Concrete Transaction/Span types
  • Concrete Transaction/Span context types

• PHP

  • Add trace() method: https://github.com/getsentry/sentry-laravel/pull/598

• Java

  • Webflux support is bad, tried https://github.com/getsentry/sentry-java/pull/2224 but that is awful DX, maybe with Java Agent magic this can be hidden and just made to work
  • Continuing a trace takes a lot of code (shouldn’t really matter if using OTEL)
  • Gradle plugin to add our integrations to a project automatically (already works for Android; not sure what needs to be done to have this for backend); if we push the Java Agent approach this might not be needed

• Javascript

  • Get rid of additional import @sentry/tracing

[HazAT]

https://github.com/getsentry/sentry-laravel/pull/598