You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Sentry already contains its own backend. It would be useful to add the possibility to generate dumps from clients using the Sentry backend. This feature can help in diagnosing issues more effectively by providing detailed crash reports directly from the clients.
Use case
User Reports: When users report crashes, generate crash dumps to reproduce and diagnose the issues they are experiencing.
Reports can't be sent: In some cases, reports are not sent to Sentry (for example, due to network issues or other problems). It would be useful to generate crash dumps to identify and reproduce the steps leading to these issues.
@EvgenPervenenko thanks for the suggestion! I can definitely see how this could be useful for users. This is a somewhat sizable project so no promises that this will get prioritized anytime soon, but I will bring up your idea internally. For now, I'll leave this ticket open to gauge interest from the rest of the community.
Problem Statement
Description
Sentry already contains its own backend. It would be useful to add the possibility to generate dumps from clients using the Sentry backend. This feature can help in diagnosing issues more effectively by providing detailed crash reports directly from the clients.
Use case
User Reports: When users report crashes, generate crash dumps to reproduce and diagnose the issues they are experiencing.
Reports can't be sent: In some cases, reports are not sent to Sentry (for example, due to network issues or other problems). It would be useful to generate crash dumps to identify and reproduce the steps leading to these issues.
Interface Changes
add function
sentry_write_minidump_to(const std::string &pathToDump, callback)
using:
sentry_write_minidump_to(path_to_dump, [](const std::string &pathToDump){
});
Solution Brainstorm
No response
Product Area
Unknown
The text was updated successfully, but these errors were encountered: