newrelic / newrelic/newrelic-java-agent
Agent fails to recover gracefully from network connection failures (ConnectionPoolTimeoutException)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
Description
There exists scenarios where network connection errors causes the agent to fail to recover gracefully and stop reporting data.
As such the goal here is to provide more extensive error handling.
Acceptance Criteria
To accomplish this goal, we will investigate this try-catch block in our agent code base to include more scenarios.
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 in newrelic-agent/src/main/java/com/newrelic/agent/RPMService.java around the try-catch block at line 819. Review how network failures, including ConnectionPoolTimeoutException, are handled and identify the additional scenarios that prevent the agent from reporting data. Done means the agent recovers gracefully instead of stopping telemetry reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100