influxdata / influxdata/kapacitor
Write an Kapacitor OOM investigation runbook
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Write a runbook for diagnosing (or gathering diagnostic input) Kapacitor OOMs. What are common reasons K might run out of memory - and how to check for them.
Contributor guide
Research direction
Start from the issue body and the Kapacitor repository context, then identify common causes of Kapacitor out-of-memory conditions and the diagnostic information maintainers need. Done means a runbook explains how to investigate or collect input for each relevant cause, with actionable checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, observability-sre
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100