newrelic / newrelic/newrelic-java-agent
Log Priority Sampling filter that will capture only ERROR and WARN logs `max_samples_stored` if limit exceeded
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
This customer was encountering a situation where their log ingest was surpassing the maximum threshold for max_samples_stored. When this happened, they lost visibility into critical errors. They would like to see a log level filter added to our current Priority Sampling logic, which would allow for capturing ERROR and WARN logs in the event that the max_samples_stored threshold is exceeded.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current Priority Sampling logic and its max_samples_stored threshold handling. Determine where log levels are available, then verify that ERROR and WARN logs remain capturable when the threshold is exceeded without changing normal sampling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100