Appearance
Forward data to InfluxDB
InfluxDB forwarding writes point data to a selected organization and bucket. Connection settings use a URL, organization, bucket, and token.
Configure the connection
A Manager or Owner can create an InfluxDB profile under Organization → Data → Data Forwarding.
| Field | Value |
|---|---|
| URL | InfluxDB service address reachable from the cloud |
| Organization | Organization name in InfluxDB |
| Bucket | Destination bucket name |
| Token | A token with write access to that bucket |
An InfluxDB organization and a cloud platform organization are separate resources; their names do not need to match. Use the reachable service address rather than the receiving server's localhost address.
Data mapping
| Reported field | Written as |
|---|---|
measurement, or agri_id if absent | Measurement name |
agri_id, the_type | Tags when present |
value | Point value field |
t or time | Record timestamp |
Check timestamps and query windows after writing, particularly conversion between seconds, milliseconds, and nanoseconds. The current web form has no time-precision option. If timestamps are wrong, ask the platform administrator to check the connection's time handling rather than merely expanding the query range.
Verify writes
- Enable the profile and produce new device data.
- Select the destination organization and bucket in InfluxDB.
- Query by the new message's time and measurement, and check values, tags, and timestamps.
- Check platform sent counts and receiver logs.
Writes fail
Check the URL, token permissions, organization, and bucket. If sent counts increase but your usual query is empty, check measurement names, query range, and timestamp precision.
See Forwarding profiles for credential changes and pausing.
