Modbus and Mimir 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 sends Telegraf metrics directly to Grafana’s Mimir database using HTTP, providing scalable and efficient long-term storage and analysis for Prometheus-compatible metrics.

Integration details

Modbus

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

Mimir

Grafana Mimir supports the Prometheus Remote Write protocol, enabling Telegraf collected metrics to be efficiently ingested into Mimir clusters for large-scale, long-term storage. This integration leverages Prometheus’s well-established standards, allowing users to combine Telegraf’s extensive data collection capabilities with Mimir’s advanced features, such as query federation, multi-tenancy, high availability, and cost-efficient storage. Grafana Mimir’s architecture is optimized for handling high volumes of metric data and delivering fast query responses, making it ideal for complex monitoring environments and distributed systems.

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]},
  ]

Mimir

[[outputs.http]]
  url = "http://data-load-balancer-backend-1:9009/api/v1/push"
  data_format = "prometheusremotewrite"
  username = "*****"
  password = "******"
  [outputs.http.headers]
     Content-Type = "application/x-protobuf"
     Content-Encoding = "snappy"
     X-Scope-OrgID = "****"

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.

Mimir

  1. Enterprise-Scale Kubernetes Monitoring: Integrate Telegraf with Grafana Mimir to stream metrics from Kubernetes clusters at enterprise scale. This enables comprehensive visibility, improved resource allocation, and proactive troubleshooting across hundreds of clusters, leveraging Mimir’s horizontal scalability and high availability.

  2. Multi-tenant SaaS Application Observability: Use this plugin to centralize metrics from diverse SaaS tenants into Grafana Mimir, enabling tenant isolation and accurate billing based on resource usage. This approach provides reliable observability, efficient cost management, and secure multi-tenancy support.

  3. Global Edge Network Performance Tracking: Stream latency and availability metrics from globally distributed edge servers into Grafana Mimir. Organizations can quickly identify performance degradation or outages, leveraging Mimir’s fast querying capabilities to ensure optimal service reliability and user experience.

  4. Real-Time Analytics for High-Volume Microservices: Implement Telegraf metrics collection in high-volume microservices architectures, feeding data into Grafana Mimir for real-time analytics and anomaly detection. Mimir’s powerful querying enables teams to detect anomalies and quickly respond, maintaining high service availability and performance.

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