microsoft / microsoft/gctoolkit
Add source information to events (source file, line number)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
Our application can identify areas of concern in a log file, and having the ability to direct the user to the specific line(s) in the source file where the problem occurs would improve the user experience.
Describe the solution you'd like
At a minimum the starting line number added to the GCEvent. Adding an end line is optional, but might be useful.
We currently only use the SingleGCLogFile source in our application, but those using the RotatingGCLogFile may want to have the source filename/path available as well.
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 tracing how GCEvent objects are created and how SingleGCLogFile and RotatingGCLogFile provide source information. Determine how the starting line, optional end line, and source filename or path should be represented, then verify that parsed events expose the requested locations for both source types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100