Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Document which event fields dont make sense to be set on a transaction #317

Open
marandaneto opened this issue Apr 28, 2021 · 1 comment

Comments

@marandaneto
Copy link
Contributor

The docs on transaction mention that "Transactions are Events enriched with Span data". Does it imply that all event fields are valid and make sense on transaction? For example, would having exception data make sense on transaction? Currently, it's not clear what is the actual contract of the transaction payload.

Source #221

@krystofwoldrich
Copy link
Member

krystofwoldrich commented Oct 13, 2022

We should list fields that are set on the error event but not for transactions.

Example: IO, exception these are not on transaction.

Update https://develop.sentry.dev/sdk/performance, https://develop.sentry.dev/sdk/event-payloads/transaction/

@krystofwoldrich krystofwoldrich moved this from Needs Discussion to Backlog in Mobile & Cross Platform SDK Oct 13, 2022
@kahest kahest moved this from Backlog to Done in Mobile & Cross Platform SDK Dec 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants