A PHP client library for reading from and writing to InfluxDB 1.x time series databases.
influxdb-php is a client library that enables PHP applications to communicate with InfluxDB 1.x instances. It solves the problem of integrating time series database operations—such as storing metrics, sensor data, or monitoring information—into PHP-based systems by providing a clean, object-oriented API for reading and writing data.
PHP developers building applications that need to store or analyze time-stamped data, such as monitoring tools, IoT platforms, or analytics dashboards that use InfluxDB as their backend.
Developers choose influxdb-php for its ease of use, feature parity with other language clients, and comprehensive support for InfluxDB 1.x features like UDP writes, query building, and administrative functions, all within a native PHP interface.
influxdb-php: A PHP Client for InfluxDB, a time series database
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers a chainable interface that simplifies constructing InfluxDB queries, making code more readable and reducing manual SQL-like string building.
Enables data ingestion via UDP for reduced latency and overhead, which is ideal for high-volume time-series data in monitoring or IoT scenarios.
Includes methods for database creation, retention policy management, and user privilege assignment, allowing full programmatic control over InfluxDB 1.x instances.
Supports writing points with configurable timestamp precision and optional tags/fields, accommodating diverse data structures without rigid schemas.
The library is officially archived in favor of the v2 client, meaning no new features, bug fixes, or security updates will be provided, posing long-term risks.
Only compatible with InfluxDB 1.x, so it cannot interact with InfluxDB 2.x's new API and Flux query language, forcing a switch for upgraded databases.
The README admits gaps in unit tests, documentation, and query builder features, requiring users to potentially implement workarounds or rely on community patches.
Examples like using exec('date +%s%N') for timestamps only work on Linux, adding complexity for cross-platform deployments and necessitating custom timestamp handling.