Trailing i on the number specifies an integer. InfluxDB supports scientific notation in float field values. The second unescaped space delimits the field set from the timestamp. The first unescaped space delimits the measurement and the tag set from the field set. Whitespace in line protocol determines how InfluxDB interprets the data point.

If your timestamps are not in nanoseconds, specify the precision of your timestamps when writing the data to InfluxDB.To ensure a data point includes the time a metric is observed (not received by InfluxDB), include the timestamp.*Data type: Unix timestamp* Important notes about timestamps If no timestamp is provided, InfluxDB uses the system time (UTC) of its host machine. InfluxDB accepts one timestamp per point. Optional – The unix timestamp for the data point. *Key data type: String **Value data type: * Float | Integer | UInteger | String | BooleanĪlways double quote string field values. Field keys are subject to naming restrictions. Field keys and string values are case-sensitive. Required – All field key-value pairs for the point. *Key data type: String **Value data type: * String Field set Tag keys are subject to naming restrictions. Tag keys and tag values are case-sensitive. Multiple tag key-value pairs are comma-delimited. Key-value relationships are denoted with the = operand. Optional – All tag key-value pairs for the point. Measurement names are case-sensitive and subject to naming restrictions.

InfluxDB accepts one measurement per point. Measurement Tag set Field set Timestamp.measurementName, tagKey = tagValue fieldKey = 'fieldValue' 1465839830100400200.Line protocol does not support the newline character in tag or field values. Lines separated by the newline character represent a single point in InfluxDB. It is a text-based format that provides the measurement, tag set, field set, and timestamp of a data point. InfluxDB uses line protocol to write data points. Examples of special characters in line protocol.

Newline mathmod