newrelic / newrelic/newrelic-java-agent
[Spike] Investigate why the name attribute on a Span event is missing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
Description
We had a reported issue where the name attribute was not present on a Span event.
After looking into it, it seems to have something to do with exception that are captured via Spring ExceptionHandler annotations. We need to create a repro app and explore why the name attribute is missing.
Slack Thread
Repro app template (internal)
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 reading the linked Slack thread and reviewing the repro app template, then create a repro involving Spring ExceptionHandler annotations and captured exceptions. Trace why the Span event's name attribute is absent and document a reproducible explanation and the relevant agent behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100