An OPC UA client that logs industrial data from OPC UA servers to InfluxDB with buffering to prevent data loss.
Influx-OPCUA-logger is an OPC UA client designed to log industrial data from OPC UA servers to InfluxDB. It solves the problem of reliable data collection in factory environments by buffering data during connectivity issues, ensuring no data loss. The tool supports various data types and logging methods, making it versatile for different industrial monitoring needs.
Industrial engineers, factory automation specialists, and IoT developers who need to collect and log time-series data from OPC UA servers to InfluxDB in production environments.
Developers choose this for its proven reliability in production since 2016, built-in data buffering to prevent loss, and ease of deployment as a single binary without external dependencies.
An OPCUA Client for logging data to 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.
Has been running in production factories since 2016, as stated in the README, ensuring robustness and trustworthiness in industrial environments.
Features an internal buffering mechanism that stores data during InfluxDB outages, preventing data loss—a key focus highlighted in the project description.
Deployable as a single binary with no host system dependencies, simplifying installation and reducing setup complexity across Windows, Linux, and macOS.
Supports both polled (interval-based) and monitored (on-change) value logging, allowing adaptation to different OPC UA data collection needs, as detailed in the configuration section.
Version 2 is labeled as an alpha release in the README, meaning it may have bugs or unstable features, making it risky for immediate production use without thorough testing.
Requires editing TOML or JSON config files without a GUI, which can be error-prone and time-consuming for users unfamiliar with file-based setups.
Only logs raw data with basic type support (numbers, booleans, strings) and lacks built-in features for data enrichment, filtering, or advanced transformations.
Includes 'phone home' functionality for anonymous usage data by default, which requires setting an environment variable to disable, potentially raising privacy concerns in sensitive environments.