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.

Sign up for GitHub

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

Jump to bottom

[Crashtracker]: simplify on fork #562

Open
danielsn opened this issue Jul 31, 2024 · 0 comments
Open

[Crashtracker]: simplify on fork #562

danielsn opened this issue Jul 31, 2024 · 0 comments

Comments

@danielsn
Copy link
Contributor 

          Is there any situation where we wouldn't call both `clear_trace_ids` and `clear_span_ids`? Would it make sense to combine them together? Perhaps with `ddog_crashtracker_reset_counters`? All of them claim to need to be called after a fork, so is it weird to make API users hunt down all of these one by one?

Originally posted by @ivoanjo in #551 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielsn