Supported protocols in InfluxDB
This page documents an earlier version of InfluxDB. InfluxDB v2.6 is the latest stable version.
InfluxData supports the following protocols for interacting with InfluxDB:
CollectD protocol support in InfluxDB
The collectd input The collectd input allows InfluxDB to accept data transmitted in collectd native format. This data is transmitted over UDP. A note on UDP/IP buffer sizes If you’re running Linux or FreeBSD, please adjust your operating system UDP buffer size limit, see here for more details. Configuration Each collectd input allows the binding address, target database, and target retention policy to be set. If the database does not exist, it will be created automatically when the input is initialized.
Graphite protocol support in InfluxDB
The Graphite Input A Note On UDP/IP OS Buffer Sizes If you’re using UDP input and running Linux or FreeBSD, please adjust your UDP buffer size limit, see here for more details. Configuration Each Graphite input allows the binding address, target database, and protocol to be set. If the database does not exist, it will be created automatically when the input is initialized. The write-consistency-level can also be set. If any write operations do not meet the configured consistency guarantees, an error will occur and the data will not be indexed.
OpenTSDB protocol support in InfluxDB
OpenTSDB Input InfluxDB supports both the telnet and HTTP OpenTSDB protocol. This means that InfluxDB can act as a drop-in replacement for your OpenTSDB system. Configuration The OpenTSDB inputs allow the binding address, target database, and target retention policy within that database, to be set. If the database does not exist, it will be created automatically when the input is initialized. If you also decide to configure retention policy (without configuration the input will use the auto-created default retention policy), both the database and retention policy must already exist.
Prometheus endpoints support in InfluxDB
Prometheus remote read and write API support Note: The Prometheus API Stability Guarantees states that remote read and remote write endpoints are features listed as experimental or subject to change, and thus considered unstable for 2.x. Any breaking changes will be included in the InfluxDB release notes. InfluxDB support for the Prometheus remote read and write API adds the following HTTP endpoints to InfluxDB: /api/v1/prom/read /api/v1/prom/write Additionally, there is a /metrics endpoint configured to produce default Go metrics in Prometheus metrics format.
UDP protocol support in InfluxDB
The UDP Input A note on UDP/IP OS buffer sizes Some operating systems (most notably, Linux) place very restrictive limits on the performance of UDP protocols. It is highly recommended that you increase these OS limits to at least 25MB before trying to run UDP traffic to your instance. 25MB is just a recommendation, and should be adjusted to be inline with your read-buffer plugin setting. Linux Check the current UDP/IP receive buffer default and limit by typing the following commands:
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.