getappmap / getappmap/appmap-js
Indexer quits with `SIGTERM`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
In telemetry we're seeing a bunch of instances where the indexer quits with SIGTERM. At first I thought they were manual quits, now I'm not so certain. Unfortunately, all of those come without any log output. It would be great if we had some more data from the telemetry — at least the time it was running (or a start event), maybe also memory usage? Maybe it's possible to get a backtrace from the indexer?
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 locating the indexer’s existing telemetry and SIGTERM handling, then inspect which lifecycle and resource data are currently emitted. Determine which signals can be collected reliably, such as runtime, start events, memory usage, or a backtrace. Done means SIGTERM exits provide additional diagnostic telemetry without losing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100