Log structured, machine-readable information about the results of an MMTC correlation run
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- Enhance the Run History File to include information about executions that did not complete successfully, including a JSON object containing structured information about the run
- Writing the aforementioned JSON file to stdout & the log file
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 Run History File handling and the entry point for an MMTC correlation run, then trace how unsuccessful executions and logging are represented. Done means failed and completed runs include structured JSON information in the Run History File, stdout, and the log file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100