zoom_in Click to enlarge

InfluxDB

▲ ▼

description InfluxDB Overview

InfluxDB is a purpose-built time-series database optimized for storing and querying metrics, sensor data, and other time-stamped information. Its TICK stack (Time, InfluxDB, Chronos, Kad) provides a comprehensive solution for data ingestion, storage, and analysis, making it ideal for IoT, monitoring, and analytics applications. Its known for its speed and efficiency in handling high-volume time-series data.

help InfluxDB FAQ

Should a new InfluxDB project use Flux, InfluxQL, or SQL?

That depends on the InfluxDB generation: InfluxDB 2 commonly uses Flux, while InfluxDB 3 emphasizes SQL and InfluxQL. Flux queries are not directly portable to the InfluxDB 3 query API, so the target version should be chosen before building dashboards.

How is data written into InfluxDB?

InfluxDB commonly accepts line protocol, where each point contains a measurement, tags, fields, and a timestamp. Telegraf can collect system, application, and sensor metrics and write them in this format.

When would I choose InfluxDB instead of Prometheus?

InfluxDB is useful when an application needs general time-series storage, retention policies, and queries over metrics or sensor events. Prometheus is especially strong for pull-based infrastructure monitoring and works closely with Alertmanager.

Is the TICK stack still the normal InfluxDB architecture?

TICK historically meant Telegraf, InfluxDB, Chronograf, and Kapacitor. Modern InfluxData deployments may instead use the InfluxDB web interface, Grafana, or InfluxDB 3 components, so TICK is no longer the only standard arrangement.

swap_horiz

Looking for InfluxDB alternatives? Compare top competitors ranked & scored

arrow_forward