馃敄 Feature description
Add a function that generates a UUID, and add the event_id field with that UUID to the request body for making a request to Sentry.
馃帳 Pitch
Currently, the event_id is not set in the request body when issuing an event to Sentry (see
).
Despite this field being described as required by Sentry (https://develop.sentry.dev/sdk/data-model/event-payloads/) it also works without (I just tested separately). When using GlitchTip (which works with the Sentry SDK), however, it returns an error due to incorrect event_id.
Adding this field would also allow users to use GlitchTip with Appwrite through the existing Sentry-style integration.
Happy to do this and create a PR. But since it would be my first contribution ever, quick approval would be great!
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
馃敄 Feature description
Add a function that generates a UUID, and add the
event_idfield with that UUID to the request body for making a request to Sentry.馃帳 Pitch
Currently, the
event_idis not set in the request body when issuing an event to Sentry (seelogger/src/Logger/Adapter/Sentry.php
Line 105 in 25b5bd2
Despite this field being described as required by Sentry (https://develop.sentry.dev/sdk/data-model/event-payloads/) it also works without (I just tested separately). When using GlitchTip (which works with the Sentry SDK), however, it returns an error due to incorrect
event_id.Adding this field would also allow users to use GlitchTip with Appwrite through the existing Sentry-style integration.
Happy to do this and create a PR. But since it would be my first contribution ever, quick approval would be great!
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?