aws / aws/amazon-cloudwatch-agent
Windows Event Batch Size Research
- Dominant language
- Go
- Stars
- 550
- Forks
- 271
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 13
Description
Determine the suitable batch size for windows events.
Generate steady Windows event log stream
Record CPU % by the agent with different values and record the most acceptable one. Trade off here is that we want to maximize the number while minimizing CPU %
https://github.com/aws/amazon-cloudwatch-agent/blob/master/translator/translate/logs/logs_collected/windows_events/collect_list/collectlist.go#L23
Contributor guide
Research direction
Start in translator/translate/logs/logs_collected/windows_events/collect_list/collectlist.go at the linked batch-size setting. Generate a steady Windows event log stream, test different values, and record the agent's CPU percentage for each. Done means identifying and documenting the batch size that maximizes events while keeping CPU usage acceptable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100