Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending captured events should honor sending fail. #932

Open
1 of 3 tasks
stima opened this issue Jan 3, 2024 · 3 comments
Open
1 of 3 tasks

Sending captured events should honor sending fail. #932

stima opened this issue Jan 3, 2024 · 3 comments
Labels
area: core enhancement New feature or request

Comments

@stima
Copy link
Contributor

stima commented Jan 3, 2024

Description

Sending captured events should honor sending fail.

When does the problem happen

  • During build
  • During run-time
  • When capturing a hard crash

Environment

  • OS: Unrelated
  • Compiler: Unrelated
  • CMake version and config: Unrelated

Steps To Reproduce

  1. Generate crash under Sentry SDK. That should trigger unsent event inside sentry database folder
  2. Turn off networking
  3. Run Sentry SDK again.

Expected: The event is not send and event metadata is not removed, appropriate log statement raised.
Actual: Event is not send, event metadata is removed.

Log output

@supervacuus
Copy link
Collaborator

There is currently no transport transactionality of events. If an event ends up in the send queue and the transport cannot send for whatever reason, the event is lost. If your use case expects regular network unavailability and requires delivery guarantees, the transport implementation can be customized.

Send errors should be visible in the logs.

@stima
Copy link
Contributor Author

stima commented Jan 8, 2024

Thanks I would consider to look to custom transport impelementation.

@supervacuus
Copy link
Collaborator

Btw since you use crashpad, implementing a custom transport will not help you with adding delivery guarantees for crashes since the crashpad_handler uses its own transport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core enhancement New feature or request
Projects
Status: No status
Status: Needs Discussion
Development

No branches or pull requests

2 participants