MatteoGioioso / MatteoGioioso/lambda-flame
Custom runtime processes might impact the flame graph
Open
Nobody has claimed this yet.
bug
enhancement
question
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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
The issue body names no files, tests, or entry points. Start by reviewing the repository's Lambda runtime and flame-graph process handling, then reproduce the behavior with a custom runtime; the work is done when the impact is understood and an agreed fix is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, nodejs
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100