microsoft / microsoft/windows-container-tools
Log Monitor Feedback and Future Features
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 277
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone! I'm Lucille, and I'm a PM on the Windows Container team working on Log Monitor.
Our team would love to hear from the community on how to improve Log Monitor. We are currently planning for the next versions of Log Monitor and would like to hear feedback.
Here are some guiding questions we would love to hear your thoughts on:
- How are you currently using Log Monitor? What problem is it solving for you?
- What issues are you facing surrounding Log Monitor?
- What features would you like to see?
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
This is a broad request for community feedback about Log Monitor rather than an implementation task, and it names no files, tests, or entry points. Review the existing Log Monitor usage and reported issues, then turn one specific feature request into a separately scoped issue with clear acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100