对于大规模实时查询，这不是推荐的配置。为了进行查询和压缩优化、高速摄取和高可用性，您可能需要考虑Modbus 和 InfluxDB。
50 亿+
Telegraf 下载量
#1
时序数据库
来源：DB Engines
10 亿+
InfluxDB 的下载量
2,800+
贡献者
目录
输入和输出集成概述
Modbus 插件允许您使用各种通信方法从 Modbus 设备收集数据，从而增强您监控和控制工业流程的能力。
Sumo Logic 插件旨在促进将指标从 Telegraf 发送到 Sumo Logic 的 HTTP 源。通过使用此插件，用户可以在 Sumo Logic 平台上分析他们的指标数据，利用各种输出数据格式。
集成详情
Modbus
Modbus 插件通过 Modbus TCP 或 Modbus RTU/ASCII 收集离散输入、线圈、输入寄存器和保持寄存器。
Sumo Logic
此插件有助于将指标传输到 Sumo Logic 的 HTTP 源，为 HTTP 消息采用指定的数据格式。Telegraf 必须是 1.16.0 或更高版本，可以发送以多种格式编码的指标，包括 graphite、carbon2 和 prometheus。这些格式对应于 Sumo Logic 识别的不同内容类型，确保指标被正确解释以进行分析。与 Sumo Logic 集成允许用户利用全面的分析平台，从他们的指标数据中实现丰富的可视化和见解。该插件提供配置选项，例如设置 HTTP 指标源的 URL、选择数据格式以及指定超时和请求大小等附加参数，这些参数增强了数据监控工作流程的灵活性和控制性。
配置
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]},
]
Sumo Logic
[[outputs.sumologic]]
## Unique URL generated for your HTTP Metrics Source.
## This is the address to send metrics to.
# url = "https://events.sumologic.net/receiver/v1/http/"
## Data format to be used for sending metrics.
## This will set the "Content-Type" header accordingly.
## Currently supported formats:
## * graphite - for Content-Type of application/vnd.sumologic.graphite
## * carbon2 - for Content-Type of application/vnd.sumologic.carbon2
## * prometheus - for Content-Type of application/vnd.sumologic.prometheus
##
## More information can be found at:
## https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source#content-type-headers-for-metrics
##
## NOTE:
## When unset, telegraf will by default use the influx serializer which is currently unsupported
## in HTTP Source.
data_format = "carbon2"
## Timeout used for HTTP request
# timeout = "5s"
## Max HTTP request body size in bytes before compression (if applied).
## By default 1MB is recommended.
## NOTE:
## Bear in mind that in some serializer a metric even though serialized to multiple
## lines cannot be split any further so setting this very low might not work
## as expected.
# max_request_body_size = 1000000
## Additional, Sumo specific options.
## Full list can be found here:
## https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source#supported-http-headers
## Desired source name.
## Useful if you want to override the source name configured for the source.
# source_name = ""
## Desired host name.
## Useful if you want to override the source host configured for the source.
# source_host = ""
## Desired source category.
## Useful if you want to override the source category configured for the source.
# source_category = ""
## Comma-separated key=value list of dimensions to apply to every metric.
## Custom dimensions will allow you to query your metrics at a more granular level.
# dimensions = ""
</code></pre>
输入和输出集成示例
Modbus
- 基本用法：要从单个设备读取数据，请使用设备名称和 IP 地址配置它，指定从站 ID 和感兴趣的寄存器。
- 多个请求：您可以通过指定多个
[[inputs.modbus.request]]部分，定义多个请求以从单个配置中的不同 Modbus 从站设备获取数据。 - 数据处理：利用缩放功能将原始 Modbus 读数转换为有用的指标，根据需要调整单位转换。
Sumo Logic
-
实时系统监控仪表板：利用 Sumo Logic 插件将服务器的性能指标持续馈送到 Sumo Logic 仪表板中。此设置允许技术团队实时可视化系统健康状况和负载，从而通过详细的图表和指标更快地识别任何性能瓶颈或系统故障。
-
自动化警报系统：配置插件以发送指标，这些指标在 Sumo Logic 中触发针对特定阈值的警报，例如 CPU 使用率或内存消耗。通过设置自动化警报，团队可以在问题升级为严重故障之前主动解决问题，从而显着提高响应时间和整体系统可靠性。
-
跨系统指标聚合：跨不同环境（开发、测试、生产）集成多个 Telegraf 实例，并使用此插件将所有指标漏斗到中央 Sumo Logic 实例。这种聚合支持跨环境的全面分析，从而在软件开发生命周期中促进更好的监控和明智的决策。
-
带有维度跟踪的自定义指标：使用 Sumo Logic 插件发送自定义指标，其中包括标识基础设施各个方面的维度（例如，环境、服务类型）。这种精细的跟踪允许更定制的分析，使您的团队能够剖析不同应用程序层或业务功能的性能。
反馈
感谢您成为我们社区的一份子！如果您有任何一般性反馈或在这些页面上发现了任何错误，我们欢迎并鼓励您提出意见。请在 InfluxDB 社区 Slack 中提交您的反馈。
