这不是大规模实时查询的推荐配置。 为了优化查询和压缩、高速摄取和高可用性，您可能需要考虑 OPC UA 和 InfluxDB。
50 亿+
Telegraf 下载量
#1
时序数据库
来源：DB Engines
10 亿+
InfluxDB 下载量
2,800+
贡献者
目录
输入和输出集成概述
OPC UA 插件提供了一个接口，用于从 OPC UA 服务器设备检索数据，从而促进有效的数据收集和监控。
Graphite 插件使用户能够通过 TCP 将 Telegraf 收集的指标发送到 Graphite。 这种集成允许使用 Graphite 强大的功能高效地存储和可视化时序数据。
集成详情
OPC UA
OPC UA 插件从使用 OPC UA 协议通信的设备检索数据，使您可以从 OPC UA 服务器收集和监控数据。
Graphite
此插件通过原始 TCP 将指标写入 Graphite，从而将 Telegraf 收集的指标无缝集成到 Graphite 生态系统中。 使用此插件，用户可以配置多个 TCP 端点以进行负载均衡，从而确保指标传输的高可用性和可靠性。 使用前缀自定义指标命名以及利用各种模板选项的能力增强了数据在 Graphite 中表示方式的灵活性。 此外，对 Graphite 标签的支持以及对指标名称进行严格清理的选项允许进行强大的数据管理，以满足用户的各种需求。 对于希望利用 Graphite 强大的指标存储和可视化功能，同时保持对数据表示的控制的企业来说，此功能至关重要。
配置
OPC UA
[[inputs.opcua]]
## Metric name
# name = "opcua"
#
## OPC UA Endpoint URL
# endpoint = "opc.tcp://localhost:4840"
#
## Maximum time allowed to establish a connect to the endpoint.
# connect_timeout = "10s"
#
## Maximum time allowed for a request over the established connection.
# request_timeout = "5s"
# Maximum time that a session shall remain open without activity.
# session_timeout = "20m"
#
## Security policy, one of "None", "Basic128Rsa15", "Basic256",
## "Basic256Sha256", or "auto"
# security_policy = "auto"
#
## Security mode, one of "None", "Sign", "SignAndEncrypt", or "auto"
# security_mode = "auto"
#
## Path to cert.pem. Required when security mode or policy isn't "None".
## If cert path is not supplied, self-signed cert and key will be generated.
# certificate = "/etc/telegraf/cert.pem"
#
## Path to private key.pem. Required when security mode or policy isn't "None".
## If key path is not supplied, self-signed cert and key will be generated.
# private_key = "/etc/telegraf/key.pem"
#
## Authentication Method, one of "Certificate", "UserName", or "Anonymous". To
## authenticate using a specific ID, select 'Certificate' or 'UserName'
# auth_method = "Anonymous"
#
## Username. Required for auth_method = "UserName"
# username = ""
#
## Password. Required for auth_method = "UserName"
# password = ""
#
## Option to select the metric timestamp to use. Valid options are:
## "gather" -- uses the time of receiving the data in telegraf
## "server" -- uses the timestamp provided by the server
## "source" -- uses the timestamp provided by the source
# timestamp = "gather"
#
## Client trace messages
## When set to true, and debug mode enabled in the agent settings, the OPCUA
## client's messages are included in telegraf logs. These messages are very
## noisey, but essential for debugging issues.
# client_trace = false
#
## Include additional Fields in each metric
## Available options are:
## DataType -- OPC-UA Data Type (string)
# optional_fields = []
#
## Node ID configuration
## name - field name to use in the output
## namespace - OPC UA namespace of the node (integer value 0 thru 3)
## identifier_type - OPC UA ID type (s=string, i=numeric, g=guid, b=opaque)
## identifier - OPC UA ID (tag as shown in opcua browser)
## tags - extra tags to be added to the output metric (optional); deprecated in 1.25.0; use default_tags
## default_tags - extra tags to be added to the output metric (optional)
##
## Use either the inline notation or the bracketed notation, not both.
#
## Inline notation (default_tags not supported yet)
# nodes = [
# {name="", namespace="", identifier_type="", identifier="", tags=[["tag1", "value1"], ["tag2", "value2"]},
# {name="", namespace="", identifier_type="", identifier=""},
# ]
#
## Bracketed notation
# [[inputs.opcua.nodes]]
# name = "node1"
# namespace = ""
# identifier_type = ""
# identifier = ""
# default_tags = { tag1 = "value1", tag2 = "value2" }
#
# [[inputs.opcua.nodes]]
# name = "node2"
# namespace = ""
# identifier_type = ""
# identifier = ""
#
## Node Group
## Sets defaults so they aren't required in every node.
## Default values can be set for:
## * Metric name
## * OPC UA namespace
## * Identifier
## * Default tags
##
## Multiple node groups are allowed
#[[inputs.opcua.group]]
## Group Metric name. Overrides the top level name. If unset, the
## top level name is used.
# name =
#
## Group default namespace. If a node in the group doesn't set its
## namespace, this is used.
# namespace =
#
## Group default identifier type. If a node in the group doesn't set its
## namespace, this is used.
# identifier_type =
#
## Default tags that are applied to every node in this group. Can be
## overwritten in a node by setting a different value for the tag name.
## example: default_tags = { tag1 = "value1" }
# default_tags = {}
#
## Node ID Configuration. Array of nodes with the same settings as above.
## Use either the inline notation or the bracketed notation, not both.
#
## Inline notation (default_tags not supported yet)
# nodes = [
# {name="node1", namespace="", identifier_type="", identifier=""},
# {name="node2", namespace="", identifier_type="", identifier=""},
#]
#
## Bracketed notation
# [[inputs.opcua.group.nodes]]
# name = "node1"
# namespace = ""
# identifier_type = ""
# identifier = ""
# default_tags = { tag1 = "override1", tag2 = "value2" }
#
# [[inputs.opcua.group.nodes]]
# name = "node2"
# namespace = ""
# identifier_type = ""
# identifier = ""
## Enable workarounds required by some devices to work correctly
# [inputs.opcua.workarounds]
## Set additional valid status codes, StatusOK (0x0) is always considered valid
# additional_valid_status_codes = ["0xC0"]
# [inputs.opcua.request_workarounds]
## Use unregistered reads instead of registered reads
# use_unregistered_reads = false
Graphite
# Configuration for Graphite server to send metrics to
[[outputs.graphite]]
## TCP endpoint for your graphite instance.
## If multiple endpoints are configured, the output will be load balanced.
## Only one of the endpoints will be written to with each iteration.
servers = ["localhost:2003"]
## Local address to bind when connecting to the server
## If empty or not set, the local address is automatically chosen.
# local_address = ""
## Prefix metrics name
prefix = ""
## Graphite output template
## see https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
template = "host.tags.measurement.field"
## Strict sanitization regex
## This is the default sanitization regex that is used on data passed to the
## graphite serializer. Users can add additional characters here if required.
## Be aware that the characters, '/' '@' '*' are always replaced with '_',
## '..' is replaced with '.', and '\' is removed even if added to the
## following regex.
# graphite_strict_sanitize_regex = '[^a-zA-Z0-9-:._=\p{L}]'
## Enable Graphite tags support
# graphite_tag_support = false
## Applied sanitization mode when graphite tag support is enabled.
## * strict - uses the regex specified above
## * compatible - allows for greater number of characters
# graphite_tag_sanitize_mode = "strict"
## Character for separating metric name and field for Graphite tags
# graphite_separator = "."
## Graphite templates patterns
## 1. Template for cpu
## 2. Template for disk*
## 3. Default template
# templates = [
# "cpu tags.measurement.host.field",
# "disk* measurement.field",
# "host.measurement.tags.field"
#]
## timeout in seconds for the write connection to graphite
# timeout = "2s"
## Optional TLS Config
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Use TLS but skip chain & host verification
# insecure_skip_verify = false
输入和输出集成示例
OPC UA
-
基本配置：使用您的 OPC UA 服务器端点和所需的指标设置插件。 这允许 Telegraf 开始从配置的节点收集指标。
-
节点 ID 设置：使用配置指定特定节点（例如温度传感器），以实时监控其值。 例如，配置节点
ns=3;s=Temperature以直接收集温度数据。 -
组配置：通过将多个节点分组在一个配置下，简化对它们的监控——这为该组中的所有节点设置默认值，从而减少设置中的冗余。
Graphite
-
动态指标可视化：Graphite 插件可用于将来自各种来源的实时指标（例如应用程序性能数据或服务器运行状况指标）馈送到 Graphite 中。 这种动态集成使团队能够创建交互式仪表板，以可视化关键绩效指标、跟踪随时间变化的趋势，并做出数据驱动的决策以提高系统性能。
-
负载均衡指标收集：通过在插件中配置多个 TCP 端点，组织可以为指标传输实施负载均衡。 此用例确保指标交付既有弹性又有效，从而降低了高流量期间数据丢失的风险，并保持了向 Graphite 的可靠信息流。
-
自定义指标标记：通过支持 Graphite 标签，用户可以使用 Graphite 插件来增强指标的粒度。 使用相关信息（例如应用程序环境或服务类型）标记指标，可以进行更精细的查询和分析，使团队能够深入研究特定感兴趣的领域，以获得更好的运营见解。
-
增强的数据清理：利用插件的严格清理选项，用户可以确保其指标名称符合 Graphite 的要求。 这种主动措施消除了指标名称中无效字符可能引起的问题，从而实现了更清洁的数据管理和更准确的可视化。
反馈
感谢您成为我们社区的一份子！ 如果您有任何一般性反馈或在这些页面上发现了任何错误，我们欢迎并鼓励您提供意见。 请在 InfluxDB 社区 Slack 中提交您的反馈。
