Reference · built on requestConnectorDatabases & warehouses

InfluxDB

Time series rows from InfluxDB 3 databases, written in line protocol and read with SQL or InfluxQL over HTTP or Flight.

Request accessPricing ↗

About

InfluxDB is a time series database from InfluxData. InfluxDB 3 Core is the open source release; InfluxDB 3 Enterprise, Cloud Serverless, Cloud Dedicated, and Clustered build on it. Data arrives as line protocol, a table name, optional tags, required fields, and an optional timestamp, posted to /api/v3/write_lp or to the v1 and v2 compatible write endpoints. Queries run in SQL at /api/v3/query_sql, in InfluxQL at /api/v3/query_influxql, or through Arrow Flight clients. Files persist as Parquet in object storage or on local disk.

Through Fibric, an operator runs the SQL you write over the databases and tables you name and reads the rows back as JSON lines. When it wants to write, it proposes a batch of line protocol or a database change for your approval, and the connector posts it once.

This is a reference listing. It documents what Fibric would read from InfluxDB and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from SQL sent to /api/v3/query_sql with db and q, in json, jsonl, csv, parquet, or pretty format
  • Rows from InfluxQL sent to /api/v3/query_influxql for queries carried over from v1 or v2
  • Parameterized query results, with values passed in the params object of a POST body
  • Query results streamed through Arrow Flight and Flight SQL clients
  • Databases and their retention periods through GET /api/v3/configure/database
  • Last Value Cache and Distinct Value Cache contents for the tables you configure them on

Proposed actions

  • Target capability: propose writing a batch of line protocol to POST /api/v3/write_lp with db and precision set
  • Target capability: propose creating a database with a retention period through POST /api/v3/configure/database
  • Target capability: propose a Last Value Cache or Distinct Value Cache on a table

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch a machine's vibration for early wear

    Sensor gateways write line protocol every second. The operator queries a rolling window per asset with SQL, compares the series against its baseline, and drafts a maintenance proposal when the trend breaks.

    With Predictive Maintenance

  • Trim peak demand from interval meter data

    Interval readings land in a table. The operator sums load by site over each bucket with SQL, reads the tariff window, and proposes the load shift for your approval.

    With Peak Demand

  • Catch a feed that stopped writing

    The operator reads the Last Value Cache for each tag set and lists devices whose latest timestamp is older than the expected interval.

    With Data Freshness, Sensor Health

  • Stay under the database and table limits

    The operator lists databases and retention periods through the configure endpoint and proposes a shorter retention period or a new database when a table approaches the column or table limit.

    With Storage Growth

Requirements

  • An InfluxDB 3 instance reachable over HTTP: Core, Enterprise, Cloud Serverless, Cloud Dedicated, or Clustered
  • An admin token, or a token permitted on the databases you name. The first admin token is the operator token named _admin
  • For writes, line protocol that fits the table schema. accept_partial defaults to true, so bad lines are reported and the others written
Authentication
A token created with influxdb3 create token, sent as Authorization: Bearer on v3 endpoints or Authorization: Token on v2 compatible endpoints.

Limits

  • InfluxDB 3 Core allows 5 databases per instance, 2000 tables across them, and 500 columns per table including time
  • Retention periods enforce at query time: rows past the period leave results before the retention service deletes them from storage
  • Table names, tag keys, tag values, and field keys are limited to 64KB. String field values are limited to 1MB
  • Historical query capability, high availability, and read replicas are Enterprise features. Core does not include them

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request InfluxDB ↗

Questions and answers

Which query languages does InfluxDB 3 accept?
SQL through /api/v3/query_sql and InfluxQL through /api/v3/query_influxql. Both take db and q, accept GET with URL parameters or POST with a JSON body, and return json, jsonl, csv, parquet, or pretty. Flight SQL clients query over Arrow Flight.
How are timestamps handled on write?
The precision parameter on /api/v3/write_lp accepts auto, nanosecond, microsecond, millisecond, or second. auto is the default and detects precision from the magnitude of the value. All timestamps are stored as nanoseconds. A successful write returns 204 No Content.
What does a retention period do?
It sets the maximum age of data in a database. Rows past it are filtered from queries and later deleted by the retention enforcement service. Units run from h to y; m and s are not accepted. none means data never expires, and 0d marks all data for deletion.
Ask about InfluxDB

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with InfluxDB through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy