max number of records/lines to send in a batch
OptionalconsistencyInfluxDB Enterprise write consistency as explained in https://docs.influxdata.com/enterprise_influxdb/v1.9/concepts/clustering/#write-consistency
Optionaldefaultdefault tags, unescaped
base for the exponential retry delay
delay between data flushes in milliseconds, at most batch size records are sent during flush
OptionalgzipWhen specified, write bodies larger than the threshold are gzipped
OptionalheadersHTTP headers that will be sent with every write request
max size of a batch in bytes
the maximum size of retry-buffer (in lines)
max count of retries after the first write fails
maximum delay when retrying write (milliseconds)
max time (millis) that can be spent with retries
minimum delay when retrying write (milliseconds)
randomRetry indicates whether the next retry delay is deterministic (false) or random (true).
The deterministic delay starts with minRetryDelay * exponentialBase and it is multiplied
by exponentialBase until it exceeds maxRetryDelay.
When random is true, the next delay is computed as a random number between next retry attempt (upper)
and the lower number in the deterministic sequence. random(retryJitter) is added to every returned value.
add random(retryJitter) milliseconds delay when retrying HTTP calls
WriteFailed is called to inform about write errors.
the instance of the API that failed
write error
failed lines
count of already failed attempts to write the lines (1 ... maxRetries+1)
expiration time for the lines to be retried in millis since epoch
a Promise to force the API to use it as a result of the flush operation, void/undefined to continue with default retry mechanism
WriteRetrySkipped is informed about lines that were removed from the retry buffer to keep the size of the retry buffer under the configured limit (maxBufferLines).
lines that were skipped
Options used by WriteApi .