Skip to content

🚀 Feature: Set event_id in Sentry Adapter so it also works with GlitchTip #42

@cloudatlas9

Description

@cloudatlas9

🔖 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

$requestBody = [
).

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?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions