Modbus and VictoriaMetrics Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider Modbus and InfluxDB.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

The Modbus plugin allows you to collect data from Modbus devices using various communication methods, enhancing your ability to monitor and control industrial processes.

This plugin enables Telegraf to efficiently write metrics directly into VictoriaMetrics using the InfluxDB line protocol, leveraging the performance and scalability features of VictoriaMetrics for large-scale time-series data.

Integration details

Modbus

The Modbus plugin collects discrete inputs, coils, input registers, and holding registers via Modbus TCP or Modbus RTU/ASCII.

VictoriaMetrics

VictoriaMetrics supports direct ingestion of metrics in the InfluxDB line protocol, making this plugin ideal for efficient real-time metric storage and retrieval. The integration combines Telegraf’s extensive metric collection capabilities with VictoriaMetrics’ optimized storage and querying features, including compression, fast ingestion rates, and efficient disk utilization. Ideal for cloud-native and large-scale monitoring scenarios, this plugin offers simplicity, robust performance, and high reliability, enabling advanced operational insights and long-term storage solutions for large volumes of metrics.

Configuration

Modbus

[[inputs.modbus]]
  name = "Device"
  slave_id = 1
  timeout = "1s"
  configuration_type = "register"
  discrete_inputs = [
    { name = "start", address = [0]},
    { name = "stop", address = [1]},
    { name = "reset", address = [2]},
    { name = "emergency_stop", address = [3]},
  ]
  coils = [
    { name = "motor1_run", address = [0]},
    { name = "motor1_jog", address = [1]},
    { name = "motor1_stop", address = [2]},
  ]
  holding_registers = [
    { name = "power_factor", byte_order = "AB", data_type = "FIXED", scale=0.01, address = [8]},
    { name = "voltage", byte_order = "AB", data_type = "FIXED", scale=0.1, address = [0]},
    { name = "energy", byte_order = "ABCD", data_type = "FIXED", scale=0.001, address = [5,6]},
    { name = "current", byte_order = "ABCD", data_type = "FIXED", scale=0.001, address = [1,2]},
    { name = "frequency", byte_order = "AB", data_type = "UFIXED", scale=0.1, address = [7]},
    { name = "power", byte_order = "ABCD", data_type = "UFIXED", scale=0.1, address = [3,4]},
    { name = "firmware", byte_order = "AB", data_type = "STRING", address = [5, 6, 7, 8, 9, 10, 11, 12]},
  ]
  input_registers = [
    { name = "tank_level", byte_order = "AB", data_type = "INT16", scale=1.0, address = [0]},
    { name = "tank_ph", byte_order = "AB", data_type = "INT16", scale=1.0, address = [1]},
    { name = "pump1_speed", byte_order = "ABCD", data_type = "INT32", scale=1.0, address = [3,4]},
  ]

VictoriaMetrics

[[outputs.influxdb]]
  ## URL of the VictoriaMetrics write endpoint
  urls = ["http://localhost:8428"]

  ## VictoriaMetrics accepts InfluxDB line protocol directly
  database = "db_name"

  ## Optional authentication
  # username = "username"
  # password = "password"
  # skip_database_creation = true
  # exclude_retention_policy_tag = true
  # content_encoding = "gzip"

  ## Timeout for HTTP requests
  timeout = "5s"

  ## Optional TLS configuration
  # tls_ca = "/path/to/ca.pem"
  # tls_cert = "/path/to/cert.pem"
  # tls_key = "/path/to/key.pem"
  # insecure_skip_verify = false

Input and output integration examples

Modbus

  1. Basic Usage: To read from a single device, configure it with the device name and IP address, specifying the slave ID and registers of interest.
  2. Multiple Requests: You can define multiple requests to fetch data from different Modbus slave devices in a single configuration by specifying multiple [[inputs.modbus.request]] sections.
  3. Data Processing: Utilize the scaling features to convert raw Modbus readings into useful metrics, adjusting for unit conversions as needed.

VictoriaMetrics

  1. Cloud-Native Application Monitoring: Stream metrics from microservices deployed on Kubernetes directly into VictoriaMetrics. By centralizing metrics, organizations can perform real-time monitoring, rapid anomaly detection, and seamless scalability across dynamically evolving cloud environments.

  2. Scalable IoT Data Management: Use the plugin to ingest sensor data from IoT deployments into VictoriaMetrics. This approach facilitates real-time analytics, predictive maintenance, and efficient management of massive volumes of sensor data with minimal storage overhead.

  3. Financial Systems Performance Tracking: Leverage VictoriaMetrics via this plugin to store and analyze metrics from financial systems, capturing latency, transaction volume, and error rates. Organizations can rapidly identify and resolve performance bottlenecks, ensuring high availability and regulatory compliance.

  4. Cross-Environment Performance Dashboards: Integrate metrics from diverse infrastructure components—such as cloud instances, containers, and physical servers into VictoriaMetrics. Using visualization tools, teams can build comprehensive dashboards for end-to-end performance visibility, proactive troubleshooting, and infrastructure optimization.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration