newrelic / newrelic/elixir_agent
Track Transaction across message passing
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 268
- Forks
- 107
- Avg merge
- 9h 5m
- Merged PRs (30d)
- 2
Description
Right now a "Transaction" is tracked across spawned processes, so work done in the child process is included in the Transaction.
It would be useful if we could safely track work done during message passing to the Transaction. There are risks however:
- The process would need to be "untracked" as soon as the message is handled
- All message passing is async, so the Transaction might be done already by the time the message is handled
Using seq_trace in addition to the current mechanism might enable this...
From #249
Contributor guide
No contributing guide indexed for this repository
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 existing Transaction tracking mechanism and the context from issue #249. Investigate whether seq_trace can safely cover asynchronous message handling, including prompt untracking and transactions that finish before a message is handled; done requires a defined, safe behavior for these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100