Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Make tombstone merge timestamp threshold configurable

Open Beginner friendly
#6,145 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java, kotlin
Domain
backend-api-design, mobile

Research direction

The threshold is fixed in NativeEventCollector.java lines 32-41. Start by reading that file to understand the current logic. Then modify it to accept a configurable value, likely via SentryOptions. Check for existing configuration patterns in the codebase. Ensure the change maintains backward compatibility. Run any related tests in the sentry-android-core module to verify.

Written by the indexing model from the issue text.

Description

Improvement Java Platform: Java

Tombstone merging currently requires the tombstone and native crash timestamps to be within five seconds. A 5.786-second gap prevented the merge, leaving a signalhandler event with a thin native stack instead of TombstoneMerged.

Allow configuring or increasing the threshold to improve merge reliability. The threshold is currently fixed in NativeEventCollector.

Dominant language
Kotlin
Stars
1.4k
Forks
478
Avg merge
3d 2h
Merged PRs (30d)
70

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-java

All issues in getsentry/sentry-java

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.