ImperialCollegeLondon / ImperialCollegeLondon/virtual_ecosystem
Review logging output
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 34
Description
**Is your feature request related to a problem? Please describe.**
Once we've got `vr_run` working with all of the core models, we should review the logging in a successful run to see:
* What information is missing from the log?
* Are the different levels (`INFO`, `DEBUG` and maybe `WARNING`) in a successful run log being used consistently?
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 running vr_run successfully with all core models, then inspect the resulting log output at INFO, DEBUG, and WARNING levels. Identify missing information and inconsistent level usage; done means the review findings are documented and any agreed logging changes are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100