influxdata / influxdata/influxdb
Community Questions 02/05
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
- [x] https://community.influxdata.com/t/influxdb-error-http-tls-handshake-error-from-x-x-x-x-eof/17968/3
- [ ] https://community.influxdata.com/t/query-too-slow-when-group-by-small-time-interval/18003
- [ ] https://community.influxdata.com/t/influx-freezes-vm-maxing-out-memory/17960/5
- [ ] https://community.influxdata.com/t/deleting-data-that-hasnt-updated-in-the-last-7-days/18067
- [x] https://community.influxdata.com/t/influx-v2-telegraf-configuration-on-docker/17557/8
- [x] https://community.influxdata.com/t/use-influxdb-docker-container-in-a-commercial-product/18132/2
- [ ] https://community.influxdata.com/t/batch-kapacitor-tick-to-influx-2/18144/4
Thank you!
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 with the four unchecked Community Questions links in the issue, especially the threads about slow grouping, VM memory use, deleting old data, and batch Kapacitor writes. Read each thread and its context before deciding what response or follow-up is needed; the checklist is complete when the remaining questions have been addressed and marked done.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100