Allow data collection with inspectIT collectd Integration
In order to allow the inspectIT Host Agent integration with collectd (see System performance statistics over collectd) to report data to the monitoring database, please perform the following configurations.
Find the file /etc/influxdb/influxdb.conf and find the collectd plugin configuration and change it according to the following:
### ### [collectd] ### ### Controls one or many listeners for collectd data. ### [[collectd]] enabled = true bind-address = ":8096" #port = 8096 database = "inspectit_collectd" typesdb = "/usr/share/collectd/types.db" # The path to the collectd types.db file # bind-address = "" # database = "" # typesdb = "" # These next lines control how batching works. You should have this enabled # otherwise you could get dropped metrics or poor performance. Batching # will buffer points in memory if you have many coming in. # batch-size = 1000 # will flush if this many points get buffered # batch-pending = 5 # number of batches that may be pending in memory # batch-timeout = "1s" # will flush at least this often even if we haven't hit buffer limit # read-buffer = 0 # UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
Please be sure to restart InfluxDB to apply the changes.
Batch sizes
The default batch size is 1000, pending batch factor is 5, with a batch timeout of 1 second. This means the input will write batches of maximum size 1000, but if a batch has not reached 1000 points within 1 second of the first point being added to a batch, it will emit that batch regardless of size. The pending batch factor controls how many batches can be in memory at once, allowing the input to transmit a batch, while still building other batches. (taken from official influxDB documentation)
UDP buffer size limits
Check the suggestions on the https://github.com/influxdata/influxdb/blob/master/services/udp/README.md#a-note-on-udpip-os-buffer-sizes to correctly setup your Operating system UDP buffer size limits.