A buffered output plugin for Fluentd that sends time-series data to InfluxDB.
fluent-plugin-influxdb is a buffered output plugin for Fluentd that sends log and event data to InfluxDB for time-series storage. It solves the problem of efficiently transferring time-stamped data from Fluentd's log collection pipeline into InfluxDB's specialized database for monitoring, analytics, and visualization.
DevOps engineers, SREs, and developers using Fluentd for log aggregation who need to store and analyze time-series data in InfluxDB for monitoring, metrics, or observability purposes.
Developers choose this plugin because it provides a reliable, configurable, and production-ready integration between Fluentd and InfluxDB, with buffered output for data integrity, flexible data mapping, and support for InfluxDB features like retention policies and SSL.
A buffered output plugin for fluentd and InfluxDB
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages Fluentd's buffering system with configurable chunk sizes and retry logic, ensuring data integrity during network failures or InfluxDB downtime, as detailed in the buffer configuration section.
Supports automatic mapping of Fluentd tags to InfluxDB measurements or explicit specification via the 'measurement' parameter, plus options for tag_keys and auto_tags to control data organization.
Enables use of InfluxDB-specific features like retention policies and precise timestamp control with time_precision settings, enhancing data management for time-series analysis.
Includes SSL/TLS support with use_ssl and verify_ssl parameters, along with user authentication, providing secure data transfer to InfluxDB instances in production.
Requires specific Ruby versions per the compatibility table, and for Ruby 2.0 or earlier, an additional 'cause' gem must be installed manually, adding installation complexity.
With numerous options for mapping, buffering, and InfluxDB settings (e.g., tag_keys, sequence_tag), setup can be error-prone and time-consuming for users new to both tools.
Primarily targets InfluxDB 1.x, with no mention of support for InfluxDB 2.x features like Flux queries or token-based authentication, which could hinder adoption in modern stacks.