newrelic / newrelic/newrelic-java-agent
Java AWS lamba: include "caused by" sections in a recorded stack trace
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
Is your feature request related to a problem? Please describe.
Currently, the Java lambda layer component only records the top level exception trace without any nested "caused by" exceptions.
Lambda Code
Internal slack thread
Feature Description
Modify the lambda layer code to capture the full stack trace, including nested caused by traces, up to a certain line limit (300 lines in the agent). An example of how this was accomplished in an agent's logging modules is here.
Priority
Please help us better understand this feature request by choosing a priority from the following options:
[Nice to Have, Really Want, Must Have, Blocker]
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 with src/main/java/com/newrelic/opentracing/aws/SpanUtil.java at the linked line and compare the stack-trace handling with Log4j1ExceptionUtil.java in the Java agent. Done means the Java Lambda layer records nested "caused by" exceptions in the full trace, capped at 300 lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100