getsentry / getsentry/sentry-javascript
Use tail workers to send Sentry events
- Langage dominant
- TypeScript
- Étoiles
- 8.7k
- Forks
- 1.8k
- Merge moyen
- 1 j 17 h
- PR mergées (30 j)
- 515
Description
### Problem Statement
Right now the events are send directly inside the users worker and increases at least the network requests to Sentry
### Solution Brainstorm
Using a [tail worker](https://developers.cloudflare.com/workers/observability/logs/tail-workers/) where the events are getting send to Sentry could offload at least the network requests to Sentry.
We would also retrieve additional events, which would not be captured on the worker level.
### Additional Context
It would need some investigation if there would be any benefits performance wise.
### Priority
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start by locating where Sentry events are sent directly from the users worker, then review the linked Cloudflare tail workers documentation. Investigate whether moving delivery changes performance and which additional events become available. Done should include a decided and validated approach for tail-worker-based event delivery.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- observability-sre
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100