InfluxDB users struggle to control metric volume and write targets
Teams running load tests can generate metrics fast enough to put pressure on InfluxDB disk capacity, while Home Assistant users want to send sensor data to multiple databases or instances. The built-in integration’s single-target limitation leaves some users building custom Node-RED flows, and the k6 signal describes manually watching disk usage to avoid hitting a configured limit. A small InfluxDB-compatible gateway could address both needs by filtering writes and forwarding them to multiple destinations.
For teams and Home Assistant power users sending telemetry to InfluxDB. Mentioned from Apr 2020 to Nov 2025 on product forums and GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 7.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
the disk usage of our InfluxDB increases > 1 GB/hour when our test is running. Unless we pay extra attention, the disk usage could reach to the limit (we set it to 100 GB) any time, like at midnight or on weekends
I use good old Node-Red to send data to InfluxDB. Bit of a hassle to setup initially (pull each sensor in NR, do some transformation to build the right message etc.) but has been running for several months now without issues
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks