Log structured, machine-readable information about the results of an MMTC correlation run
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- observability, tooling
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.
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
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from NASA-AMMOS/MMTC
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NASA-AMMOS/MMTC#117 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
NASA-AMMOS/MMTC#113 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
NASA-AMMOS/MMTC#106 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
NASA-AMMOS/MMTC#104 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
NASA-AMMOS/MMTC#102 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
spring-projects/spring-grpc#442 ·
-
Expose numberOfPermits in RateLimiterEvent.toString() and the ratelimiterevents actuator DTOPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
resilience4j/resilience4j#2547 ·
Maintainers usually reply within 9 days
-
Clock.MakeDate continues execution and returns a rolled-over instant after dispatching error on invalid datePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
mit-cml/appinventor-sources#4155 ·
Maintainers usually reply within 1 day