influxdata / influxdata/kapacitor
Kapacitor sizing documentation?
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hi .
I'm looking for basic sizing information, and I can't see nothing on the official documentation site (https://docs.influxdata.com/kapacitor/v1.2/introduction/). I would like to know sizing on some tipical use cases.
My use case will be similar to this:
1.- Subscribing on a InfluxDB with 100K time series, and applying 2 or 3 stream rules for each serie ( 1 point / minute)
2.- ingesting graphite 100k graphite metrics, and also applying 2 or 3 stream rules for each serie ( 1 point / minute)
Greatest monitoring time window should be in both cases no more than 1 hour.
What cpu/memory /I/O networking and disk should be necessary for a good kapacitor performance?
Should I install 2 separate processes one for each data source? or can I use only one kapacitor process?
Thank you very much
Contributor guide
Research direction
Start by reviewing the Kapacitor 1.2 introduction documentation and the sizing scenarios described in the issue. Done should provide documented CPU, memory, I/O, network, and disk guidance for the two workloads, plus guidance on using one or separate Kapacitor processes.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100